Search

Search pages, services, tech stack, and blog posts

Cloudflare Workers

Cloudflare Workers ToolingJavaScript at the edge, globally distributed

Cloudflare Workers runs your code in 300+ data centres worldwide — zero cold starts, sub-millisecond latency, and access to KV, R2, D1, Durable Objects, and Queues from the same runtime.

Cloudflare Workers runs your code in 300+ data centres worldwide with zero cold starts and sub-millisecond startup latency. Your JavaScript, TypeScript, Rust, or WASM code executes at the edge — closest to your users — with access to KV (key-value), R2 (object storage), D1 (SQLite), Durable Objects (stateful coordination), and Queues from the same runtime. At A Major, we build edge-first APIs, middleware, and full-stack applications on Cloudflare Workers. The Workers platform is uniquely powerful for latency-sensitive applications. Unlike traditional serverless (Lambda), Workers have no cold starts and bill per-request at fractions of a cent. Combined with Hono or tRPC for routing, Drizzle for D1 queries, and R2 for file storage, Cloudflare Workers is a complete edge computing platform.

Quick start

bash
npm create cloudflare@latest my-worker
cd my-worker
npm run dev

Read the full documentation at developers.cloudflare.com/workers/

300+ edge locations

Code runs within milliseconds of your users on Cloudflare's global network — latency measured in single digits.

Zero cold starts

V8 isolates spin up in under 5ms — no container boot time, every request is fast from the first byte.

KV, R2, D1 storage

Key-value store, S3-compatible object storage, and SQLite at the edge — persistent data without external services.

Durable Objects

Stateful serverless with strong consistency — coordination, WebSockets, and counters at the edge.

Hono & tRPC compatible

Use Hono for routing and tRPC for type-safe APIs — modern frameworks that run natively on Workers.

Queues & Cron

Message queues for async processing and cron triggers for scheduled tasks — background work without servers.

Why it's hard

Execution time and memory limits

Workers have CPU time limits (10ms free, 30s paid) and 128MB memory. Long-running computations need to be split across multiple requests or moved to Durable Objects.

Node.js API compatibility gaps

Workers use the V8 runtime, not Node.js. Some Node.js APIs (fs, net, child_process) aren't available. The nodejs_compat flag helps but doesn't cover everything.

Local development fidelity

Wrangler's local dev mode (Miniflare) simulates the Workers runtime but edge cases around bindings and runtime behavior may differ from production.

Stateful patterns require Durable Objects

Workers are stateless by default. Coordination, counters, rate limiting, and WebSocket state require Durable Objects — a different programming model.

Best practices

Use Hono for Workers routing

Hono is built for edge runtimes — lightweight, fast, and provides Express-like routing with middleware on Workers.

Use D1 for relational data at the edge

Cloudflare D1 runs SQLite in the same data centre as your Worker — eliminates database round-trip latency entirely.

Cache aggressively with the Cache API

Workers have access to Cloudflare's Cache API. Cache API responses, KV lookups, and computed results to minimize re-execution.

Use Wrangler for deployment and configuration

wrangler.toml defines bindings, routes, and environment variables. Use wrangler dev for local development and wrangler deploy for production.

Frequently asked questions




Want to build with Cloudflare Workers?

Talk to our engineering team about your Cloudflare Workers architecture. We'll respond within 24 hours.

1 spot available in May 2026Apr 2026 fully booked

We limit intake each month so every project gets the focus it deserves.