ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Cloudflare Workers KV delivers sub-10 ms reads at the edge, see a concrete feature-flag worker example, and understand when its eventual consistency model fits your workload.
Design a minimal, stateless API that stores session data in Workers KV. Learn how to bind KV, handle eventual consistency, monitor limits, and when to move to Durable Objects.
Cloudflare Workers KV offers a globally distributed key-value store ideal for read-heavy caching. This blog walks through binding KV implementing a cache-aside pattern and practical limits to watch.
Cloudflare Workers provides a compatibility boundary for Node.js APIs, allowing developers to target specific runtime versions. Transitioning from Node.js 16 to Node.js 18 introduces changes in how built-in modules are resolved and how the runtime handles fetch behavior. When deploying in unbundled mode, the availability of specific Node.js polyfills varies.
Cloudflare Workers utilizes the V8 ICU implementation, allowing Intl.DateTimeFormat to accept IANA time zone names for regional date conversion. While this supports standard formatting, the Date object remains anchored to UTC timestamps. A technical uncertainty arises during Daylight Saving Time (DST) transitions, specifically when a local time occurs twice
Goal Determine whether a Worker can safely reuse a Hyperdrive-managed database connection across separate HTTP requests when each request may run in a different Cloudflare Workers isolate. Cloudflare Workers execute in ephemeral isolates, so a connection stored in globalThis may be discarded between requests. Hyperdrive centralizes PostgreSQL and MySQL pooli
Wrangler v3 flipped the default for wrangler dev to remote mode, which requires an authenticated Cloudflare login and uploads code to a preview URL. A team that previously relied on the v2 local default now needs to decide how to run Worker integration tests in CI without production credentials. Local mode still executes the Worker in workerd/Miniflare on th
Migration Goal A small application currently hosted on a traditional backend must be moved to Cloudflare Workers while serving live traffic. The plan uses Workers Routes with percentage-based weights to shift requests gradually from the origin to the new Worker script, avoiding a hard DNS cutover. Constraints and Uncertainty Workers KV provides only eventual
Goal: Achieve consistent regional timestamp handling in a Cloudflare Worker so that all business logic sees times in a chosen zone while the underlying Date object remains UTC. Constraints: The Workers runtime provides only the ECMAScript Date API, which always returns UTC values and ignores any TZ environment variable; explicit zone conversion must be perfo
cloudflareworkers
nodejs