Durable Objects: Don't Tempt Fate, Maintain State
summary
Durable Objects run on Cloudflare Workers, keep per-key state in memory with on-disk persistence, and serialize all requests to avoid races; a live demo shows a collaborative drawing room that stores up to 1,000 strokes and uses websockets for real‑time sync, and a counter example scaffolds voting via an auto-provisioned object bound to a name. Code is generated with DeepSeek and published on GitHub; region pinning and single-threaded execution deliver strong consistency and reduced latency across the Edge.
AI-written summary · about
chapters (14)
- 0:00Durable Objects intro
- 1:25Why developers need them
- 5:20Name debate and actor model
- 7:15Pain of managing state
- 8:18How Durable Objects solve it
- 10:29Programming model and actors
- 12:45Live demo: drawing app
- 17:05Coffee voting app build
- 24:41How they work under the hood
- 26:50Key advantages over serverless
- 28:57When to use Durable Objects
- 29:41Durable Objects vs KV store
- 30:25Future of stateful Edge Computing
- 31:31Summary
related talks
30mWebSockets: The Real-Time Avengers
17mImmutable offline webapps
58mAdvanced Serverless Workflows with Durable Functions
14mOvercoming Serverless challenges with Durable Functions
01h 14mSustainable, Maintable and Durable. Azure Durable...
48mDelightful Durable Function Patterns
15mDurable Functions: Semantics for Stateful Serverless
41mBuilding Durable Serverless IoT Device Workflows using Cloud
