Durable Objects
A stateful edge computing primitive introduced by Cloudflare. Each instance is globally unique and provides strong consistency, enabling coordination of shared state across Workers and supporting stateful serverless application scenarios.
Core Facts
Cloudflare Durable Objects assign a globally unique ID to each object and guarantee that all requests with the same ID are routed to the same instance, thereby achieving strongly consistent state storage.
Durable Objects are stateful compute units on the Cloudflare Workers platform; each object has its own in-memory state and persistent storage, and only one instance of the same object ID runs at any given time.
Timeline (last 90 days)
The Deno team released the first version of celld in August, their open-source implementation of the Durable Objects pattern in Cloudflare Workers.
The risk of building applications around the Workers programming model and the Durable Objects pattern is decreasing, because it has gained stronger official backing.
The Agents SDK provides a built-in SQL interface for Durable Objects.
Each Durable Object instance is identified by a string ID; the same ID always routes to the same instance, and different IDs are completely independent.
In-memory JavaScript variables, uncommitted transactions, temporary tables, and prepared statements within Durable Objects are not persisted when the DO hibernates.
Cloudflare Workers + Durable Objects latency is in the single-digit millisecond range, but query capabilities are limited (a SQL subset with no support for joins or complex transactions).
The recommended hybrid architecture is to use Durable Objects for short-term context and homelab/Qdrant for long-term knowledge, establishing a memory hierarchy and using TTL policies to clean up expired session data.
Durable Objects automatically hibernate when there are no requests for a few seconds, saving memory state via checkpointing, dropping CPU usage to zero, with wake-up time ranging from 10–100 ms depending on state size.
The design constraint of the hibernation mechanism is: never rely on in-memory state surviving between requests, and all critical state must be written to persistent storage before returning.
There are three main isolation models for Durable Objects: Per-Session, Per-User, and Per-Tenant.
6 more timeline events
All Facts (18)
Cloudflare Durable Objects assign a globally unique ID to each object and guarantee that all requests with the same ID are routed to the same instance, thereby achieving strongly consistent state storage.
65%VerifiedDurable Objects are stateful compute units on the Cloudflare Workers platform; each object has its own in-memory state and persistent storage, and only one instance of the same object ID runs at any given time.
65%UnverifiedCloudflare Workers生态中的Durable Objects为有状态的Agent工作流提供强一致性的状态存储
90%UnverifiedEach Durable Object instance is identified by a string ID; the same ID always routes to the same instance, and different IDs are completely independent.
50%UnverifiedThere are three main isolation models for Durable Objects: Per-Session, Per-User, and Per-Tenant.
50%UnverifiedThe Agents SDK provides a built-in SQL interface for Durable Objects.
50%UnverifiedIn-memory JavaScript variables, uncommitted transactions, temporary tables, and prepared statements within Durable Objects are not persisted when the DO hibernates.
50%UnverifiedCloudflare Workers + Durable Objects latency is in the single-digit millisecond range, but query capabilities are limited (a SQL subset with no support for joins or complex transactions).
50%UnverifiedThe recommended hybrid architecture is to use Durable Objects for short-term context and homelab/Qdrant for long-term knowledge, establishing a memory hierarchy and using TTL policies to clean up expired session data.
50%UnverifiedDurable Objects automatically hibernate when there are no requests for a few seconds, saving memory state via checkpointing, dropping CPU usage to zero, with wake-up time ranging from 10–100 ms depending on state size.
50%UnverifiedThe design constraint of the hibernation mechanism is: never rely on in-memory state surviving between requests, and all critical state must be written to persistent storage before returning.
50%UnverifiedDurable execution means that a workflow's execution state can be serialized and saved, allowing it to resume from a checkpoint after an interruption or failure without having to rerun from the beginning.
50%UnverifiedCloudflare's storage and data products include R2 for object storage, the SQLite database D1, key-value storage KV, and Durable Objects for stateful computing.
50%UnverifiedK2 very likely uses Durable Objects as the storage and coordination layer for partition state, combined with R2 for message persistence.
50%UnverifiedCloudflare's Serverless ecosystem includes Workers (serverless compute), Durable Objects (stateful objects), R2 (object storage), and Queues (message queues).
50%UnverifiedThe Deno team released the first version of celld in August, their open-source implementation of the Durable Objects pattern in Cloudflare Workers.
50%UnverifiedThe risk of building applications around the Workers programming model and the Durable Objects pattern is decreasing, because it has gained stronger official backing.
50%UnverifiedCloudflare announced that starting from the compatibility date of October 1, 2026, Durable Objects will allow Agents to continue running after the client disconnects as long as there are still pending input/output tasks
50%