Working on some examples of Lambda durable functions to help my understanding. Also trying to summarise key concepts. So far… API Gateway, CDK, microservice orchestration, strategy-pattern workflow, tests and async callback Next: state machine/chart, eventbridge github.com/lukehedger/l...

Lambda Managed Instances just announced! > AWS Lambda Managed Instances lets you run Lambda functions on your Amazon EC2 instances while maintaining Lambda's operational simplicity aws.amazon.com/about-aws/wh...

Finally! We can programmatically get a set of IAM permission needed for an AWS API call aws.amazon.com/about-aws/wh...

You guys the talk i did last week was kinda fire. Here’s a clip

Introducing Serverless @resonatehqio.bsky.social Build distributed, durable applications with Resonate's dead simple programming model, Distributed Asynchronous Await Now on serverless

Really interesting writeup from @unkey.com on their serverless exit. Let’s dig into the detail… www.unkey.com/blog/serverl...

I am kinda feeling like durable execution is going to be a very boring thing that's tablestakes at some point in the next N years (where N < 5).

hey @schickling.dev if I use @livestore.dev as an event-sourcing framework, am I locked into using SQLite as the event store or is this swappable? docs.livestore.dev/evaluation/e...

Need to take a closer look but @livestore.dev can be used as an “event-sourcing framework” docs.livestore.dev/evaluation/e...

Seen this in a few places now… is single node the future of (most) backend software engineering? topicpartition.io/definitions/...

If you’re not familiar with @tigerbeetle.com (and TigerStyle) this is a great introduction! And even if you are it’s a good read www.amplifypartners.com/blog-posts/w...

AWS Lambda is making a comeback

Is anyone implementing the OCI runtime spec in Zig?

Serverless ... can go fuck itself.

New blog post, reflecting on nearly seven years since the Firecracker launch, and how we're using Firecracker to power serverless databases (in Aurora DSQL) and infrastructure for AI agents (in Bedrock AgentCore). Here's the post: brooker.co.za/blog/2025/09...

Cool to see @cedardb.com will offer S3 object storage as an option for persistence cedardb.com/docs/get_sta...

yet another launcher github.com/klaatu01/yal

Some starter SQL queries I put together for trying out Iceberg tables on S3 with Athena github.com/lukehedger/i...

Just ran `bun index.ts` without installing node_modules first and amazed that it *just worked*. Then found out about auto-install. Nice feature @bun.sh! "Under Bun-style module resolution, packages are auto-installed on the fly into a global module cache during execution" bun.com/docs/runtime...

Are you using ULID or UUID v7?

What do teams actually do about code freezes around the high shopping season? The research and armchair advice says “absolutely not”. But on the ground I see lots of nervousness about releasing code for days, weeks and even months around key dates

Always wondered what a MFA token generator does when I’m not looking at it

Paxos-as-a-service would be handy! “very few customers… are going to ask Amazon for Paxos-as-a-service... AWS should return to its roots and release important building blocks — the things customers will need, not necessarily what they're asking for”

Bemused by the enthusiastic embrace of JSON-RPC by the LLM tools ecosystem.

The biggest lie in Software Engineering Undo There’s no undo Only a new Do that resembles the old state The past is immutable We just pile on a new present

Apache Iggy looks super promising. Following the trend of building streaming around an append-only log iggy.apache.org/docs/introdu...

Oldie but a goodie

I love where Zed is going to. And the vision of DeltaDB can improve a lot of the missing capabilities of Git. Some weeks ago, I shared a way we are using Git to not lose knowledge between commits. Will it be possible to do something like this in Zed? learnings.aleixmorgadas.dev/p/extending-...

@zed.dev is building a database for linking software engineering artifacts (commits, ADRs, chats, calls) to arbitrary lines of code. It’s called DeltaDB and uses CRDTs zed.dev/blog/sequoia...

It’s quite simple really. The handler function signatures are slightly different from one cloud provider to another but it’s real easy boilerplate to handle the differences. Access to path, query parameters, body and headers are very similar. The responses are even easier.

CTOs used to not get fired for buying IBM, now they get uneasy about vendor lock-in. But is buying from vendors still a safer bet than relying on OSS for your most critical infra?

Is @nitric.io the new, cooler SST? At first glance, the API looks neater nitric.io

More on jazz’s backendless approach… super interesting! 🎷

Not heard this one before but it’s got a nice ring to it — from @jazz.tools > backendless

AGENT.md seems like a good idea

Time Flies is surprisingly absorbing. Afterwards found myself looking at a real fly and wondering what bucket list items they were getting thru

Or how about zero-server architecture?

Quite like “scale to zero” as an alternative to the term “serverless” This is from the @basetenco.bsky.social docs

void is my new best friend

Remember when io.js was forked from node.js?

Ooo yeah! 🙌 Abstraction layers and internal platforms built on top of solid foundational primitives will give you evolvable software. Although I’d advocate for vendor-specific primitives over OSS (like k8s and tf). OSS is fine as you move up the stack but you want reliability at the base

The new OpenAI open weights models are available in Amazon Bedrock and SageMaker JumpStart. In Bedrock, you can use them also via an OpenAI-compatible endpoint. More info in my post: buff.ly/8dRMPG9 #AWS #AI #GenAI #OpenAI #OpenSource

Vibe code is legacy code blog.val.town/vibe-code

I've been trying to articulate why the fawning, complimentary responses from AI chatbots feel so insidious to me. I've finally figured out how to explain it. Wrote a long piece on how current model training and design choices threaten our critical thinking skills: maggieappleton.com/ai-enlighten...

Yeah, never believe the hype around any technology! Running a HA, distributed backend on Lambda will never be perfect but if you take the time to understand serverless you can reach high levels (not hyper!) of scale and rest very easy

Will read this paper purely out of respect for the title

Our Star Wars quickstart got good feedback, and now you can view the stream from the dashboard too 🫣 This comes in real handy for live debugging and observability — especially in systems built around agentic workflows, microservices, or event sourcing using @s2.dev

The two most common things you hear said about serverless: * there are still servers * it’s just FaaS That said, I’m seeing more innovation in the serverless space in 2025 than the past 3/4 years. Hopefully the balanced, informed discussions will follow!

Hot on the heels of Toad comes Crush, which looks super cool. Loving this trend of custom terminal apps for driving LLMs. Warp 2.0 also looks promising. Need to find time to try them all out! github.com/charmbracele...