cloudflare-workers

Cloudflare Workers enable you to build serverless edge functions deployed globally across Cloudflare's network. Write JavaScript handlers, configure bindings to D1, KV, R2, or Durable Objects, and deploy using Wrangler CLI for zero infrastructure management and millisecond cold starts.

Workers support fetch, cache, HTMLRewriter, and WebSockets runtime APIs, plus bindings for D1 databases, KV storage, R2 object storage, and Durable Objects for stateful logic. Configure all bindings in wrangler.toml and access them via environment variables.

Use Wrangler CLI to run Workers locally with wrangler dev, test fetch handlers and bindings in your environment, and verify behavior before production deployment. Wrangler handles environment configuration via .env and wrangler.toml.

Yes, Workers are ideal for building scalable edge API endpoints and middleware. Handle incoming requests with fetch handlers, apply transformations with HTMLRewriter, integrate with databases and storage via bindings, and deploy globally without managing servers.

Cloudflare Workers support scheduled tasks through cron triggers configured in wrangler.toml. Execute JavaScript logic on a schedule across Cloudflare's edge network with pay-per-request pricing and no infrastructure overhead.

Both formats run in V8 isolates on Cloudflare's edge. ES Modules use module syntax for cleaner code organization, while Service Worker format uses global request handlers. Choose based on your project structure; Wrangler supports both.