Cloudflare Workers

Core Philosophy

1. Edge-first means Web API-first — Write to the standard Fetch runtime model (Request, Response, fetch, URL) instead of assuming Node APIs exist.
2. Bindings are the platform contract — KV, D1, R2, Durable Objects, Queues, and AI are not ad hoc SDK calls; they are explicit runtime capabilities passed into your worker.
3. Latency beats distance — Keep hot request paths short, cache aggressively, and move coordination-heavy logic out of the edge path when possible.
4. State belongs in the right primitive — KV for simple global reads, D1 for relational queries, R2 for blobs, Durable Objects for coordination, Queues for async work.
5. Deploy safely with environments — Separate preview, staging, and production config in Wrangler; edge mistakes propagate globally fast.

Quick-Start: Common Problems

"Which Cloudflare storage primitive should I use?"