Cloudflare Durable Objects
Cloudflare Durable Objects is a serverless coordination and stateful compute primitive within Cloudflare Workers that provides a single, globally addressable instance per object ID, giving each object strongly consistent, in-memory state…
Definition
Cloudflare Durable Objects is a serverless coordination and stateful compute primitive within Cloudflare Workers that provides a single, globally addressable instance per object ID, giving each object strongly consistent, in-memory state and its own attached durable storage.
Overview
Serverless compute is traditionally stateless: each request may be handled by a different, ephemeral instance with no shared memory, which makes coordination problems — like managing a single source of truth for a chat room, a game session, or a rate limiter — awkward without an external database acting as a lock and state store. Durable Objects solve this by guaranteeing that for any given object ID (a name or ID you define), there is exactly one active instance running anywhere in Cloudflare's global network at a time, and all requests for that ID are routed to it. Because each Durable Object instance is single-threaded and holds state in memory between requests, it naturally serializes access — eliminating race conditions without explicit locking — while also providing a built-in transactional key-value storage API for persisting state durably to disk, so in-memory state can be reconstructed if the object is evicted and later re-instantiated. This combination of strong consistency, low-latency in-memory access, and durable storage make Durable Objects well suited to coordination-heavy problems that are difficult to solve efficiently with either a stateless function or a traditional external database alone. Durable Objects run on Cloudflare's edge network alongside Cloudflare Workers, and Workers route requests to a specific object using a namespace binding and an ID derived from a name or generated randomly. Because Cloudflare places the object near where it is first accessed and keeps it pinned there, applications can get low-latency access for geographically concentrated usage patterns, such as a specific user's session or a specific document being edited. Common patterns include building WebSocket-based real-time applications (each Durable Object can hold WebSocket connections for a room or session), distributed locks, rate limiters, and lightweight per-entity databases, positioning Durable Objects as a foundational building block for stateful serverless applications on Cloudflare's platform.
Key Features
- Exactly one active instance per object ID, globally, at any time
- Single-threaded execution model eliminates race conditions without explicit locks
- In-memory state combined with built-in durable, transactional storage
- Tightly integrated with Cloudflare Workers via namespace bindings
- Well suited to coordination problems like locks, counters, and rate limiters
- Supports long-lived WebSocket connections per object
- Object placement is dynamic, pinned near first access for low latency
- Part of Cloudflare's broader serverless edge compute platform