0Pricing
Edge Computing with Cloudflare Workers & Deno · Lesson

Durable Objects & Stateful Coordination

Use Durable Objects to add strongly consistent, single-instance state and coordination to otherwise stateless edge architectures.

Durable Objects & Stateful Coordination is a free Edge Computing with Cloudflare Workers & Deno lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Edge Computing with Cloudflare Workers & Deno learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

The Stateless Problem

Workers are stateless by design, each request may hit a different instance anywhere on Earth.

That is great for scale, but hard when you need:

  • A single source of truth
  • Coordination between many clients
  • Strong consistency, not eventual

Durable Objects solve exactly this.

What Is a Durable Object?

A Durable Object (DO) is a single, globally-addressable instance with its own private storage.

For a given object ID, all requests route to the same instance, giving you a consistent place to hold state.

Defining a Durable Object Class

A DO is a class with a fetch() method and access to persistent state.storage.

export class Counter {
  constructor(state, env) {
    this.state = state;
  }
  async fetch(request) {
    let count = (await this.state.storage.get('count')) || 0;
    count++;
    await this.state.storage.put('count', count);
    return new Response(String(count));
  }
}

Binding the Object

Declare the DO class as a binding in wrangler.toml and add a migration so Cloudflare knows about it.

[[durable_objects.bindings]]
name = "COUNTER"
class_name = "Counter"

[[migrations]]
tag = "v1"
new_classes = ["Counter"]

Getting an Object Stub

From a Worker, derive an ID then get a stub to talk to that specific instance.

const id = env.COUNTER.idFromName('global-counter');
const stub = env.COUNTER.get(id);
const res = await stub.fetch('https://do/increment');

idFromName vs newUniqueId

Two ways to get an ID:

  • idFromName('room-42') deterministic, same name always maps to the same object, ideal for named resources like chat rooms
  • newUniqueId() a brand-new unique object, ideal for per-session state

Strong Consistency Guarantee

Because every request for an ID hits the same instance and runs single-threaded, DO operations are strongly consistent, no race conditions on its own storage.

This makes DOs perfect for counters, locks, and leaderboards.

Coordinating Many Clients

A DO is a natural hub. Combined with WebSockets it can broadcast to all connected clients, the basis for collaborative apps and multiplayer rooms.

// Inside the DO: track sockets and fan out
this.sessions.forEach((ws) => ws.send(message));

Storage API Basics

state.storage is a transactional key-value store local to the object.

await this.state.storage.put('user:1', { name: 'Ada' });
const user = await this.state.storage.get('user:1');
await this.state.storage.delete('user:1');

Alarms for Scheduled Logic

Durable Objects support alarms, schedule the object to wake itself up later for cleanup or timeouts.

await this.state.storage.setAlarm(Date.now() + 60000);
// later, the runtime calls:
async alarm() {
  await this.cleanup();
}

When to Use Durable Objects

Reach for DOs when you need:

  • Coordination across requests or clients
  • Strong consistency on a single entity
  • Real-time rooms, locks, rate counters, or queues

For simple cached reads, KV is cheaper. Choose the right tool.

Quick Check

Which method gives you a deterministic Durable Object ID for a named resource like a chat room?

Recap

Durable Objects bring stateful coordination to the edge:

  • One globally-addressable instance per ID
  • Private transactional storage and alarms
  • Strong consistency and single-threaded execution
  • Use idFromName for named resources, newUniqueId for sessions

They are the missing piece for real-time, consistent, edge-native systems.

Frequently asked questions

Is the “Durable Objects & Stateful Coordination” lesson free?

Yes — the full text of “Durable Objects & Stateful Coordination” is free to read here on the web, and the Edge Computing with Cloudflare Workers & Deno course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Edge Computing with Cloudflare Workers & Deno course, upgrade to CoddyKit PRO.

What will I learn in “Durable Objects & Stateful Coordination”?

Use Durable Objects to add strongly consistent, single-instance state and coordination to otherwise stateless edge architectures. You practise Edge Computing with Cloudflare Workers & Deno with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Edge Computing with Cloudflare Workers & Deno?

No prior experience is required. Edge Computing with Cloudflare Workers & Deno on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Durable Objects & Stateful Coordination” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Edge Computing with Cloudflare Workers & Deno lesson?

Yes. Every Edge Computing with Cloudflare Workers & Deno lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. Microservices at the Edge
  2. Event-Driven Architectures
  3. Geolocation & Localization
  4. Durable Objects & Stateful Coordination
← Back to Edge Computing with Cloudflare Workers & Deno