Adding Security Headers Globally with Cloudflare Workers
Learn how to use Cloudflare Workers to inject security headers such as HSTS globally at the edge, with a ready‑to‑run example, deployment steps, and notes on limits and verification.
Loading…
ReadMeFeed / Community knowledge
#edge-computing
Real questions. Useful conversations. Find the people who know your stack.
cloudflareChoosing Between SSG, Edge Functions, and Serverless Functions on Netlify
Deciding between SSG, Edge Functions, and Serverless Functions on Netlify is a balance of latency and data freshness. This guide compares the three strategies to help you optimize TTFB.
netlifyArchitecting a Global Edge Cache with Cloudflare Workers and the Cache API
Learn how to implement a programmatic edge cache using Cloudflare Workers and the Cache API to reduce origin load and latency for dynamic content.
cloudflareworkersArchitecting for the Edge: Vercel Edge Functions vs. Serverless Functions
Learn how to implement Vercel Edge Functions using V8 Isolates to eliminate cold starts, including runtime limitations and the correct architectural boundaries for global data access.
nextjsUsing Cloudflare Workers KV for Low-Latency Global Caching
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.
Reducing Kubernetes Overhead: Using SQLite with K3s for Edge Deployments
Learn how K3s uses SQLite and the Kine shim to replace etcd, reducing memory overhead for edge and single-node Kubernetes deployments.
k3s
kubernetes
sqliteProtect Your APIs with Cloudflare Rate Limiting: A Practical Guide
Cloudflare Rate Limiting lets you protect API endpoints at the edge. This guide shows how to configure thresholds, bursts, and custom responses, explains trade‑offs, and gives a step‑by‑step example to help you deploy the feature safely.
K3s-only vs Mixed RKE2/K3s Strategy in Rancher for Edge-Constrained Deployments
Goal: Determine whether to standardize on K3s for all downstream clusters managed by Rancher or to adopt a mixed approach that runs RKE2 in core/regulated workloads and K3s at the edge, while respecting limited CPU and memory budgets on branch hardware. Constraints: K3s delivers a small footprint with a single binary and SQLite datastore, fitting tightly con
rancherFetch handler wall-clock timeout limits
Cloudflare Workers enforce a strict limit on the wall-clock time a fetch handler can run before the runtime terminates the request. This limit applies to both JavaScript and WebAssembly modules to ensure edge performance and resource availability. While the event.waitUntil() method allows a worker to continue performing background tasks after a response has