durable-objects

To coordinate stateful resources with Cloudflare Durable Objects, you assign one DO per coordination unit like a chat room or game session. This model uses per-entity storage and RPC methods to avoid global bottlenecks across distributed edge instances.

You set up WebSockets and SQLite storage in a Durable Object by defining them within your DO class and wiring the class to a DO binding in wrangler.json. This configuration supports real-time communication and durable state for collaborative applications.

Yes, you can test Cloudflare Durable Objects locally using Vitest. The workflow involves creating your DO class, wiring it to wrangler.json, and running wrangler dev alongside Vitest to validate RPC methods, alarms, and SQLite-backed storage.

The best use cases for stateful edge computing with Durable Objects include chat rooms, collaborative apps, real-time dashboards, and per-tenant coordination scenarios. These applications benefit from per-entity state and real-time WebSocket communication without stateless bottlenecks.

You configure alarms and RPC methods for edge applications by defining them inside your Durable Object class and registering the class through a DO binding in wrangler.json. This setup enables scheduled tasks and direct invocations across distributed instances.

You should avoid using Durable Objects for edge state management when your application requires shared global state across all users rather than per-entity coordination, as the one-DO-per-unit model is designed to isolate state for specific chat rooms, game sessions, or tenants.