durable-objects

Durable Objects provide per-entity state coordination at the edge by offering deterministic routing and SQLite-based storage. Each game instance or chat room gets a single DO to enforce consistency and manage state lifecycle independently.

Durable Objects handle WebSocket connections in Cloudflare Workers by providing per-entity storage and RPC methods. A single DO instance manages WebSocket connections for a specific room or user, ensuring real-time state coordination across clients.

Call a Durable Object by name using the getByName method on your binding, such as env.MY_DO.getByName("room-1"), then invoke RPC methods like await stub.yourRpcMethod("payload") after configuring the wrangler setup with a durable_object binding.

Cloudflare Workers supports SQLite-based storage for Durable Objects, enabling per-entity state persistence at the edge. This storage model allows each DO instance to maintain isolated state for chat rooms, booking systems, or collaborative apps.

Durable Objects support alarms and RPC methods for scheduled and on-demand state coordination at the edge. Alarms trigger time-based actions within a DO, while RPC endpoints handle method invocations like getByName and idForName for lifecycle management.

Durable Objects are not ideal for stateless request handling or scenarios lacking per-entity coordination needs. If your app requires no persistent state, real-time WebSocket coordination, or isolated per-entity storage, standard Cloudflare Workers without DO bindings are simpler.