Back to feed
Dev.to
Dev.to
7/2/2026
The original title is about durable execution and exactly-once semantics, with DBOS and TypeScript migration of 34 automations.

The original title is about durable execution and exactly-once semantics, with DBOS and TypeScript migration of 34 automations.

Original: Exactly-Once by Default: How Durable Execution Changed the Way I Build Automations

Short summary

The author migrated 34 production automations from a visual no-code platform to TypeScript using DBOS, whose durable execution ensures exactly-once semantics by default—eliminating tedious idempotency bookkeeping. Workflows automatically resume from the last completed step after crashes, guaranteeing no duplicate side effects and no lost state. This approach shifts durability from a manual per-workflow concern to a framework baseline, reducing code complexity while strengthening reliability.

  • •Durable execution with exactly-once semantics eliminates manual idempotency bookkeeping
  • •Workflows automatically resume from last checkpoint after crashes, preventing duplicates
  • •Shifts reliability from per-flow engineering concern to framework baseline

Generated with AI, which can make mistakes.

#ai-tools#ai-agents
Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

"Done" Is Not a State
Dev.to
I Deleted My No-Code Automation Platform and Rewrote 34 Workflows in TypeScript
Dev.to
The original title is "How We Make Every Scheduled Job Safe to Re-Run" which is 9 words. Let me check the rules:
Dev.to
We hit an at-least-once delivery trap. Here is how we fixed the race conditions.
Dev.to