Cloudflare Workers

1. Workers Overview and Runtime Model

   V8 isolates, edge execution model, request lifecycle, and how Workers differ from containers and traditional servers.

2. Fetch Handler

   The fetch event handler, Request and Response objects, env and ctx arguments, and ctx.waitUntil.

3. Runtime APIs

   Web-standard APIs available in Workers: fetch, streams, crypto, cache, HTMLRewriter, and Node.js compatibility.

4. Wrangler and Configuration

   wrangler.toml/jsonc configuration, environments, local development, deploying, and compatibility dates and flags.

5. Bindings

   Connecting Workers to resources such as KV, R2, D1, Queues, and service bindings via env.

6. Environment Variables and Secrets

   Plain-text variables, encrypted secrets, and per-environment configuration.

7. Routes, Domains and Static Assets

   Custom domains, route patterns, workers.dev, and serving static assets alongside Worker code.

8. Workers KV

   Eventually consistent global key-value storage, reads and writes, expiration, and caching behavior.

9. D1

   Serverless SQLite database, SQL queries from Workers, migrations, and read replication.

10. R2

    Object storage accessed from Workers via bindings, multipart uploads, and S3 compatibility.

11. Durable Objects

    Stateful single-instance objects with strongly consistent storage, WebSockets, alarms, and coordination.

12. Queues

    Message queues with producers and consumers, batching, retries, and dead letter queues.

13. Cron Triggers and Scheduled Handlers

    Scheduled handlers invoked by cron expressions for periodic background work.

14. Workflows

    Durable multi-step execution with steps, retries, sleeps, and waiting for events.

15. Workers AI and Hyperdrive

    Running AI model inference on the edge and accelerating regional databases via Hyperdrive connection pooling.

16. Observability

    Workers Logs, real-time logs, tail, traces, metrics, and error debugging.

17. Testing and Limits

    Unit and integration testing with Vitest pool workers, plus CPU time, memory, subrequest, and size limits.

Each section links to the official page. Titles and summaries by Extra Credit; the docs belong to their authors.