Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →A Durable Object is a Cloudflare Worker with attached storage and a globally unique name, so requests from different places can reach the same logical object and coordinate around shared state. Bytes #511 uses Ryan Dahl’s celld project to make that idea approachable; the key distinction is that celld is a self-hosted implementation, while Cloudflare runs its Durable Objects service.
What Bytes #511 means by “a durable object”
Bytes #511, published August 11, 2026, opens with “So… what’s a durable object?” and approaches the concept through celld, a project that offers Cloudflare-compatible Workers and Durable Objects APIs. Its simplified picture is a worker process paired with SQLite state and replicated off-machine storage. That is a useful mental model, not a complete description of Cloudflare’s product architecture. Read Bytes #511.
As an Amazon Associate I earn from qualifying purchases.
Cloudflare describes Durable Objects as “a building block for stateful applications and distributed systems.” A Durable Object combines compute with attached durable storage. Its globally unique name identifies the logical object, allowing requests from around the world to reach the same object. Cloudflare says its attached storage is strongly consistent and fast to access, making the model useful when clients or events need to coordinate through shared state. Cloudflare’s Durable Objects overview was last updated July 15, 2026.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesWhy put compute and shared state together?
A regular Worker can handle an individual request, but applications that need multiple clients or events to agree on changing state also need coordination. A Durable Object gives that work a named place to meet: for example, one object can manage the state and messages for a chat room, shared document, game session or live notification channel.
Cloudflare lists collaborative editing, chat, multiplayer games and live notifications as example uses. Its documentation describes objects as starting when needed and shutting down when idle. The design is therefore not simply “a database with code”: it is a way to associate request-handling logic and shared, strongly consistent state with a particular logical entity.
When to choose a Durable Object over a database or regular Worker
- Use a regular Worker when requests can be handled independently and do not need one coordinated, shared state owner.
- Use a database when the main requirement is persistent data storage and your application’s existing architecture already handles concurrency and coordination appropriately.
- Consider a Durable Object when requests need to serialize or coordinate updates to a shared entity, such as a room, document or game session. It can avoid making you build those coordination primitives separately.
This is an architectural distinction, not a claim that one option is always faster or cheaper. The right fit depends on the application’s state model, required APIs, usage limits and operational needs.
What celld changes—and what it does not
celld presents itself as a self-hosted system with Cloudflare-compatible Workers and Durable Objects APIs. Its project page, accessed October 7, 2026, identifies the release as v0.6.1 beta and describes support for Workers, Durable Objects, KV, Queues, D1, R2, Workflows, Cron and static assets; Containers are marked experimental. It describes per-cell SQLite databases, shared bucket storage, cell ownership leases and failover across instances. See celld’s project page.
Compatibility does not mean identical services. The project says workloads requiring Cloudflare’s network, GPUs or browser farm are out of scope. An application should be checked against the specific APIs and bindings it uses rather than assumed to work unchanged.
| Consideration | Cloudflare Durable Objects | celld |
|---|---|---|
| Who operates the infrastructure? | Cloudflare provides the hosted service. | The operator runs and troubleshoots the machines, network, bucket and fleet. |
| Storage and coordination | Cloudflare documents globally named objects with attached, strongly consistent storage. | The project describes per-cell SQLite databases, shared bucket storage, ownership leases and failover. |
| Compatibility boundary | Cloudflare’s Workers platform and its service capabilities. | Compatibility depends on celld’s supported APIs and bindings; Cloudflare-specific network, GPU and browser-farm workloads are excluded. |
| Operational visibility | Use Cloudflare’s hosted platform and its available operational tools. | The project describes inspecting ownership records, SQLite/LTX files and logs. |
The choice is fundamentally about deployment and responsibility. Cloudflare runs its hosted platform; celld gives an operator control over a self-hosted deployment along with the associated infrastructure work. Neither the shared API surface nor the project’s own test results establish equivalent reliability, latency, support, pricing or operational guarantees.
How to read celld’s performance and durability figures
celld reports its own measurements, not independent benchmarks. Its page describes a durability test using four-vCPU, 8 GB nodes and a bucket in the same region; it tests failover by stopping a loaded node with SIGKILL and checking rooms after recovery. In that described node-kill test, the project reports zero acknowledged writes lost and about 20 seconds for failover. It also reports about 90 ms durable-write latency in a one-node, region-local setup.
For a separate warm speed test, celld reports about 0.2 ms p50 and 0.3 ms p99 stateless-request latency on an Apple M-series laptop over loopback. Those conditions are not directly comparable to a hosted, globally distributed service. Treat the results as project-reported measurements for the setups described, not as a basis for claiming celld is faster, more durable or more reliable than Cloudflare.
Availability and the practical decision
Cloudflare’s overview says Durable Objects are available on Free and Paid plans. It also says SQLite-backed Durable Objects are available on the Workers Free plan subject to plan limits, and that SQLite storage methods have moved from beta to general availability. Check the current official documentation and plan details for the limits that apply to your account; the overview does not establish a universal quota or total cost for a particular workload.
Before choosing a self-hosted or hosted setup, map the application’s bindings and storage needs, identify who will operate and diagnose failures, and estimate cost using the expected traffic and writes. celld’s own base-cost comparison excludes application traffic and writes, so it is not a complete operating-cost comparison.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
