What if every entity were one small server?
A direct explanation of Durable Object identity, execution, storage, alarms, suitable tasks, consistency boundaries, and the new celld implementation.
From mechanism to evidence.
The film opens up identity, activation, event gates, private SQLite, alarms, and failure semantics; derives a workload-fit test; then tests the model with a persistent writing coach and an identity, paid-usage, and audit subsystem built from Durable Objects.
The point that matters: with celld, this model now runs outside Cloudflare — Worker code and per-object SQLite on nodes and a bucket you own, writes durable before any response, and orders of magnitude cheaper at scale by celld's own benchmarks.
7 minutes 28 seconds · 1080p · AI-generated English narration using ElevenLabs · Durable Objects — Kenton Varda & the Cloudflare Workers team · celld — Ryan Dahl & Deno Land, Apache-2.0 · github.com/denoland/celld
- The Durable Object promise
- The object boundary
- What a Durable Object is
- A callable reference
- Activation and hibernation
- Single-threaded execution and gates
- Private SQLite
- Durable alarms
- The workload-fit test
- Choose the consistency boundary
- A persistent writing coach
- One project, one object
- A failure-safe agent job
- GitHub identity as routing
- Billing inside one account object
- The cross-object saga
- How celld operates
- The reusable design question