Using Cloudflare Workers Durable Objects for Per‑User Rate Limiting
Learn how to use Cloudflare Workers Durable Objects to implement low‑latency, per‑user rate limits without an external database.
Loading…
ReadMeFeed / Community knowledge
#durable-objects
Real questions. Useful conversations. Find the people who know your stack.
cloudflareworkersBuild a Reliable Counter with Cloudflare Workers Durable Objects
Learn how to create a stateful counter that survives restarts, scales automatically, and handles concurrent increments using Cloudflare Workers Durable Objects. The guide covers setup, code, deployment, and verification.
cloudflareChoosing Cloudflare Durable Objects for Consistent State: A Decision Guide
A decision guide comparing Durable Objects, KV, D1, and external databases for consistent state in Cloudflare Workers with trade-offs, constraints, and a concrete implementation pattern.
Does Cloudflare Workers rollback reconcile Durable Object state after schema changes?
When a Workers deployment is rolled back to a prior version via the dashboard or API, the edge code package swaps atomically and propagates within roughly one minute. However, KV namespace bindings and Durable Object class definitions are not versioned alongside the code; rolling back restores the previous binding references but leaves existing KV data and D
Cloudflare Workers ↔ Durable Objects: Compatibility of lock semantics across runtime versions
Cloudflare Workers ↔ Durable Objects: Compatibility of lock semantics across runtime versions The goal is to determine whether the DurableObject.lock method behaves consistently when invoked from Cloudflare Workers running different runtime versions (e.g., 2023.12 vs newer releases). The key uncertainty lies in whether the lock acquisition order, timeout han
Cache API vs. Durable Objects for Hot-Key Read Coalescing
Managing Tail Latency Under Concurrent Load When implementing a high-traffic read endpoint in Cloudflare Workers, managing latency spikes during concurrent bursts is critical. Two documented approaches exist for handling "hot keys" to prevent origin overload and reduce tail latency: the Cache API and Durable Objects. Trade-offs in Coordination The Cache API