Skip to content(if available)orjump to list(if available)

How to think about durable execution

How to think about durable execution

4 comments

·December 12, 2025
Visit

vouwfietsman

For me the main issue with these systems is that its still seen as a special case of backend execution. I think the real value is just admitting that every POST/PUT should kick off a durable execution, but that doesn't seem to match the design, which considers these workflows quite heavy and expensive, and bases its price on it.

What we need is an opinionated framework that doesn't allow you to do anything except durable workflows, so your junior devs stop doing two POSTs in a row thinking things will be OK.

immibis

Isn't durable execution just another one of these frameworks that promises to make everything easy if you reorganise all your code into the framework?

phrotoma

Ballsy for a founder to come right out and (roughly) say "yeah anyway fuck vendors" on the corporate blog. Points for honesty.

abelanger

Hah, well I'll avoid _talking to_ vendors, more specifically I'll avoid talking to salespeople selling a technical product until we're pretty deep in the product. I do tend to not use vendors that don't have a good self-serve path or mechanism to get my technical questions answered.