ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #cloudflareworkers
Learn how to use Cloudflare Workers KV as a lightweight, globally distributed session store for stateless edge applications, including a code example, consistency trade‑offs, and practical verification steps.
Workers KV is not a strongly consistent database. Learn how to use it for global edge configuration, understand propagation delays, and avoid common pitfalls.
Step‑by‑step guide to building a Cloudflare Worker backed by a Durable Object for per‑user session state, including setup, code, local testing, deployment, verification, and rollback.
When a Cloudflare Worker needs mutable state, pick the right storage: KV for global, eventually consistent caching; Durable Objects for strong consistency, low‑latency per‑instance state. This guide compares options, explains trade‑offs, and shows a concrete example with validation steps.
When Durable Objects lose state, lag, or lose updates, the culprit is often a mis‑configured key, cold start, or race condition. This guide walks through common symptoms, ordered checks, quick fixes, and escalation steps.
Learn how to build a stateful counter with Cloudflare Workers Durable Objects, see the exact code, understand size and concurrency limits, and avoid common pitfalls.
A counter in a Worker's memory doesn't add up across locations. Here's how Durable Objects serialize per-tenant state, with a worked limiter and its limits.
Learn how to identify when a Cloudflare Worker hits the 50‑subrequest limit, why it happens, and what steps to take to reduce or raise the limit.
How the Cloudflare Workers Cache API (caches.default) stores responses per datacenter, with a working example covering ctx.waitUntil, body cloning, cache-key normalization, and the mistakes that cause silent misses.
cloudflare