A practical look at durable execution in DBOS (TypeScript): what the crash-in-the-middle problem really is, why manual idempotency is painful, and how workflows resume from the last completed step — with real code.
In the previous article I described moving 34 production automations off a visual no-code platform and rewriting them in TypeScript. The single feature that made that migration worth the effort was durable execution with exactly-once semantics. This post is the deep-dive.
The problem: a crash in the middle
Here's a scenario every automation eventually hits. A workflow receives a new lead, sends them a welcome message, then writes them to the CRM:
Send welcome message
Save to CRM
Postgres-backed durable execution (DBOS) skips the separate orchestrator and gives you transactional exactly-once for free. When…
Why I moved 34 production automations from a visual no-code platform to code-first durable workflows — the real benchmarks, the…
If you have built anything with long-running stateful workflows — loan approvals, order processing,...
Modern applications demand long‑lasting workflows that can withstand crashes, restarts, and failures,...
In the last part, we looked at how expressions make your workflows dynamic. Today, we are discussing...
Collection of Cloudflare blog posts tagged 'Durable Execution'
