PluginBench
Skill
Official
Pass
Audit score 90

durable-objects

cloudflare/skills

Build stateful, coordinated applications on Cloudflare's edge using Durable Objects.

What is durable-objects?

This skill enables building, debugging, and reviewing Cloudflare Durable Objects code for persistent state management and coordination. Use it when you need strong consistency, per-entity storage, real-time coordination, or scheduled work tied to specific entities.

  • Create and manage Durable Object classes with SQLite storage and RPC methods
  • Implement coordination patterns like chat rooms, multiplayer games, and collaborative documents
  • Configure wrangler bindings and migrations for Durable Objects
  • Design sharding strategies and parent-child relationships for scalability
  • Write and test Durable Object code with Vitest integration
  • Handle WebSocket connections, alarms, and scheduled per-entity work

How to install durable-objects

npx skills add https://github.com/cloudflare/skills --skill durable-objects
Prerequisites
  • Cloudflare Workers project with wrangler configured
  • Understanding of TypeScript and async/await patterns
  • Familiarity with SQL for SQLite schema design
Claude Code
Cursor
Windsurf
Cline

How to use durable-objects

  1. 1.Define a Durable Object class extending DurableObject with constructor initialization using blockConcurrencyWhile()
  2. 2.Configure wrangler.jsonc with durable_objects bindings and migrations specifying new_sqlite_classes
  3. 3.Create stub instances using getByName() for deterministic routing or newUniqueId() for unique instances
  4. 4.Implement RPC methods (not fetch handlers) for communication with the Durable Object
  5. 5.Use ctx.storage.sql.exec() for synchronous SQLite operations or ctx.storage for KV storage
  6. 6.Set alarms with setAlarm() for scheduled per-entity work and implement the alarm() handler
  7. 7.Test using Cloudflare's Vitest integration following the testing reference documentation

Use cases

Good for
  • Building a chat room system where each room is a separate Durable Object instance
  • Implementing an inventory or booking system requiring strong consistency guarantees
  • Creating a multiplayer game with per-game Durable Objects for state coordination
  • Developing a real-time collaborative document editor with persistent connections
  • Setting up subscription renewal or game timeout logic using alarms
Who it's for
  • Backend engineers building stateful edge applications
  • Full-stack developers implementing real-time coordination features
  • Cloudflare Workers developers needing persistent state beyond KV storage
  • Teams building multi-tenant SaaS platforms with per-entity data isolation

durable-objects FAQ

When should I use Durable Objects vs. plain Workers?

Use Durable Objects when you need strong consistency, per-entity state, coordination (chat, games, collaborative docs), persistent connections, or scheduled work tied to specific entities. Use plain Workers for stateless request handling.

What's the difference between getByName() and newUniqueId()?

getByName() creates a deterministic stub—same input always routes to the same instance, ideal for named entities like chat rooms. newUniqueId() generates a unique ID each time; store the mapping externally if you need to retrieve it later.

Can I use blockConcurrencyWhile() on every request?

No—blockConcurrencyWhile() should only be used during initialization in the constructor. Using it on every request kills throughput by serializing all operations.

Should I store critical state in memory or SQLite?

Always persist critical state to SQLite storage first. Memory state can be lost on eviction or crash. Use memory only for caching data you've already persisted.

How do I schedule recurring work in a Durable Object?

Use setAlarm() to schedule work at a specific time. In the alarm() handler, process the work and call setAlarm() again to reschedule if needed. Each Durable Object can have only one active alarm.

Full instructions (SKILL.md)

Source of truth, from cloudflare/skills.


name: durable-objects description: Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.

Durable Objects

Build stateful, coordinated applications on Cloudflare's edge using Durable Objects.

Retrieval Sources

Your knowledge of Durable Objects APIs and configuration may be outdated. Prefer retrieval over pre-training for any Durable Objects task.

ResourceURL
Docshttps://developers.cloudflare.com/durable-objects/
API Referencehttps://developers.cloudflare.com/durable-objects/api/
Best Practiceshttps://developers.cloudflare.com/durable-objects/best-practices/
Exampleshttps://developers.cloudflare.com/durable-objects/examples/
Roles and permissionshttps://developers.cloudflare.com/workers/authorization/durable-objects/

Fetch the relevant doc page when implementing features.

When to Use

  • Creating new Durable Object classes for stateful coordination
  • Implementing RPC methods, alarms, or WebSocket handlers
  • Reviewing existing DO code for best practices
  • Configuring wrangler.jsonc/toml for DO bindings and migrations
  • Writing tests with Cloudflare’s Vitest integration
  • Designing sharding strategies and parent-child relationships

Reference Documentation

  • ./references/rules.md - Core rules, storage, concurrency, RPC, alarms
  • Testing reference - Current Vitest documentation, migration choices, and test selection
  • ./references/workers.md - Workers handlers, types, wrangler config, observability

Search: blockConcurrencyWhile, idFromName, getByName, setAlarm, sql.exec

Core Principles

Use Durable Objects For

NeedExample
CoordinationChat rooms, multiplayer games, collaborative docs
Strong consistencyInventory, booking systems, turn-based games
Per-entity storageMulti-tenant SaaS, per-user data
Persistent connectionsWebSockets, real-time notifications
Scheduled work per entitySubscription renewals, game timeouts

Do NOT Use For

  • Stateless request handling (use plain Workers)
  • Maximum global distribution needs
  • High fan-out independent requests

Quick Reference

Wrangler Configuration

// wrangler.jsonc
{
  "durable_objects": {
    "bindings": [{ "name": "MY_DO", "class_name": "MyDurableObject" }]
  },
  "migrations": [{ "tag": "v1", "new_sqlite_classes": ["MyDurableObject"] }]
}

Basic Durable Object Pattern

import { DurableObject } from "cloudflare:workers";

export interface Env {
  MY_DO: DurableObjectNamespace<MyDurableObject>;
}

export class MyDurableObject extends DurableObject<Env> {
  constructor(ctx: DurableObjectState, env: Env) {
    super(ctx, env);
    ctx.blockConcurrencyWhile(async () => {
      this.ctx.storage.sql.exec(`
        CREATE TABLE IF NOT EXISTS items (
          id INTEGER PRIMARY KEY AUTOINCREMENT,
          data TEXT NOT NULL
        )
      `);
    });
  }

  async addItem(data: string): Promise<number> {
    const result = this.ctx.storage.sql.exec<{ id: number }>(
      "INSERT INTO items (data) VALUES (?) RETURNING id",
      data
    );
    return result.one().id;
  }
}

export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const stub = env.MY_DO.getByName("my-instance");
    const id = await stub.addItem("hello");
    return Response.json({ id });
  },
};

Critical Rules

  1. Model around coordination atoms - One DO per chat room/game/user, not one global DO
  2. Use getByName() for deterministic routing - Same input = same DO instance
  3. Use SQLite storage - Configure new_sqlite_classes in migrations
  4. Initialize in constructor - Use blockConcurrencyWhile() for schema setup only
  5. Use RPC methods - Not fetch() handler (compatibility date >= 2024-04-03)
  6. Persist first, cache second - Always write to storage before updating in-memory state
  7. One alarm per DO - setAlarm() replaces any existing alarm

Authorization

Durable Objects do not have separate roles or permissions; access follows the Worker that implements them. Retrieve the current Durable Objects authorization guidance before granting observability or Data Studio access, and scope the Workers role to the intended Worker or Workers product.

Anti-Patterns (NEVER)

  • Single global DO handling all requests (bottleneck)
  • Using blockConcurrencyWhile() on every request (kills throughput)
  • Storing critical state only in memory (lost on eviction/crash)
  • Using await between related storage writes (breaks atomicity)
  • Holding blockConcurrencyWhile() across fetch() or external I/O

Stub Creation

// Deterministic - preferred for most cases
const stub = env.MY_DO.getByName("room-123");

// From existing ID string
const id = env.MY_DO.idFromString(storedIdString);
const stub = env.MY_DO.get(id);

// New unique ID - store mapping externally
const id = env.MY_DO.newUniqueId();
const stub = env.MY_DO.get(id);

Storage Operations

// SQL (synchronous, recommended)
this.ctx.storage.sql.exec("INSERT INTO t (c) VALUES (?)", value);
const rows = this.ctx.storage.sql.exec<Row>("SELECT * FROM t").toArray();

// KV (async)
await this.ctx.storage.put("key", value);
const val = await this.ctx.storage.get<Type>("key");

Alarms

// Schedule (replaces existing)
await this.ctx.storage.setAlarm(Date.now() + 60_000);

// Handler
async alarm(): Promise<void> {
  // Process scheduled work
  // Optionally reschedule: await this.ctx.storage.setAlarm(...)
}

// Cancel
await this.ctx.storage.deleteAlarm();

Testing

Read the testing reference before configuring a suite or writing Durable Object tests. It routes to current setup, APIs, and examples and identifies the behavior to cover.