Luke Hedger

Looking good!

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

Could you explain resource contention?

Redis website showing “Caching. Obviously”

Love how they still recognise how synonymous Redis is with caching alongside the obligatory AI pivot

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!

The struggle is real!! 😂 So much FUD around serverless discourse. Exhausting trying to have nuanced discussions

Decorator-less API is looking really nice! Makes the control-flow easy to follow and the code read like the execution. This is one of my favourite features of durable workflows tbh - you can write/read async/branching code in a logical, ordered fashion.

Hmm yeah you’re right Qian Li. Although it looks like it _could_ become suitable for runtime apps too, maybe with a dedicated API... 🤷‍♂️ Do DAGs make sense for durable executions?

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...

Programmable Workflows | Dagger Write workflows in code, not YAML

Has @dagger.io become a universal durable execution platform? 🤔 docs.dagger.io/features/pro...

Hard agree on this but it’s a travesty. Often see teams build async apps around events/messaging but use CRUD for access patterns and mutable relational or nosql for persistence. This creates an unwieldy frankenstein. Event sourcing as a pattern is an optimal (but complex) model for state in an EDA

What if the event sourcing engine and storage were abstracted away behind a simple API with suitable primitives? So application engineers would just get the ergonomic benefits without needing to understand the mechanics.

The results… I was expecting 2 and 3 to be the winners but seems there are a lot of expert event sourcerers and lots who don’t care for it at all! Thanks for voting 💖

The results… I was expecting 2 and 3 to be the winners but seems there are a lot of expert event sourcerers and lots who don’t care for it at all! Thanks for voting 💖

iroh less net work for networks

I think you could be right. Seems like a few interesting gossip protocol projects being work on rn, like @iroh.computer www.iroh.computer/proto/iroh-g...

Do you like event sourcing?

1️⃣ Expert, use it all the time
2️⃣ Part-time user, learning the ropes
3️⃣ Would like to use but don’t know where to start
4️⃣ Not interested, next question

📊 Show results

That does sound cool! Not a python user so wondering:

* what does the RM role involve?
* how do you get the chance to be the RM?

Hope it goes well! 🇨🇦

Uncloud looks super promising in this space. The power of docker without the overhead of k8s

> no central control plane to maintain. Each machine maintains a synchronised copy of the cluster state through peer-to-peer communication

🆒

uncloud.run

Sorry to see that winglang shutdown

But I want to buy the LEGO set prebuilt Dave! 😂

bsky.app/profile/luke...

Imagine AWS EventSource existed ✨ You’d just bring your data models and state transition rules and start sending commands to and consuming events from the service. Easy

If only it were that simple Brian! I want to allow teams to get the benefits of event sourcing without needing to know how to implement the engine - like using SQS instead of building/operating a message queue yourself. That’s what is meant by “managed service”

This looks very cool Max - nice work! I’m interested in how aggregates could be generated from a set of rules. Maybe you’d define a FSM (and domain objects) in JSON and codegen the executable logic and state reconstruction. WDYT?

Does something like fully-managed event sourcing exist? I’m expecting:

* Event ingestion API
* Command/trigger API
* Event store
* Snapshotting
* Domain data models defined in code
* Aggregate generation
* State machine event handlers
* Event/CDC stream and broadcast

Drop it in and it “just works”

AI-assisted Engineering 🙋‍♂️ Not enough people talking sensibly about this!

No worries Addy - looking forward to reading the final version! Think enterprise teams especially can benefit from a framework around agentic ai usage for their engineers.

Turns out hackers don’t test their code…

> AWS Security has inspected the code and determined the malicious code was distributed with the extension but was unsuccessful in executing due to a syntax error

aws.amazon.com/security/sec...

This is so cool! 🤩