Lambda on Lambda: Serverless Haskell on AWS
A recent talk focused on using Haskell to create AWS Lambda functions. The speaker shared insights on building Haskell functions into OCI-format containers and configuring them for Lambda. The event fostered engaging discussions among attendees, highlighting the interest in functional programming.
- ▪The talk was held at the Melbourne Compose Group.
- ▪The speaker demonstrated how to implement AWS Lambda functions using Haskell.
- ▪An end-to-end example of building Haskell functions into OCI-format containers was shared.
3 outlets in our directory ran this story, first to last over 26 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Lobsters files mainly under programming. We currently carry 187 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Jackkelly |
| Canonical URL | http://jackkelly.name/blog/archives/2026/06/24/lambda_on_lambda_serverless_haskell_on_aws/index.html |
| Publication time | Mon, 25 May 2026 01:37:47 -0500 |
| Retrieval time | 2026-05-25T07:07:36.419Z |
| Last seen | 2026-05-25T07:07:36.419Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | fwGoeMNF3o2f · 3 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Lambda on Lambda: Serverless Haskell on AWS Posted on June 24, 2026 by Jack Kelly Tags: haskell, coding, talks Earlier this week, I gave a talk at the Melbourne Compose Group (mailing list) about using Haskell to implement AWS Lambda functions. Lambda is AWS’s “function-as-a-service offering”, where your code runs in an isolated “microVM” on AWS-managed infrastructure and you pay only for the resources used while your code runs. As a mature AWS service, Lambda has a lot of features and knobs, and many of the blog posts I’ve read about deploying to Lambda were closer to “draw two circles” than “how to draw the owl”. I’ve wanted to address this gap for a long time.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Jackkelly.
Discussion
0 commentsMore from Jackkelly
