Durable Executions in the Face of (some) Failures
summary
Shows a concrete pattern using Temporal workflows to run a three‑step order pipeline (create/confirm payment, fulfill, archive) with durable execution semantics: if the worker process is killed after step two the workflow resumes after worker crash and continues to completion, picking up new code changes for remaining steps. Demonstrates at‑least‑once semantics without custom retries, timers, polls or external distributed key stores, and gives runnable code and a live UI replay.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:17Example
- 0:51Error Handling
- 1:48Limitations
- 2:22Durable Execution
- 3:04Temporal Workflow
- 3:54Demo
related talks
35mBuilding resilient applications with Durable Execution
44mThe Simplest Way to Build Resilient Applications
32mWhy idempotency matters during durable execution in modern software stacks
28mStateful Applications in the Age of Durable Execution
42mHow to build distributed systems in JavaScript
23mDesigning a Workflow Engine From First Principles
01h 38mBuilding Reliable Distributed Systems
24mDurable Agents: long running AI workflows in a flakey world