ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Workers KV is not a strongly consistent database. Learn how to use it for global edge configuration, understand propagation delays, and avoid common pitfalls.
Learn how to eliminate origin bottlenecks using Cloudflare Workers KV to store dynamic configuration and feature flags at the edge for sub-50ms latency.
k3OS uses a cloud‑init‑style config.yaml to turn a bare‑metal node into a fully unattended, Kubernetes‑managed machine. This post shows how to supply the file, a working example, and the trade‑offs of using an archived distribution.
k3OS provides RAM-only, immutable k3s nodes provisioned from a single k3os.yaml. It is useful for disposable edge and CI workloads, but the project is archived since 2022 with no security updates.
Learn how to run edge‑based A/B tests with Cloudflare Workers, see a concrete Worker example, and understand the CPU‑time and caching limits.
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.
Feature-flag lookups don't need an origin round-trip. Here's how to serve them from Cloudflare Workers KV, with a worked routing example and the consistency trade-offs you must design around.
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.
Workers KV removes the origin round trip from session lookups, but its consistency model decides your logout behavior, your cache settings, and when you need Durable Objects instead.
cloudflareworkers
cloudflare
kubernetes
k3os
k3s