Written from your Cloudflare note for the interview on 14 October 2026. General questions about how Cloudflare's developer platform works and when to use which product. What Cloudflare does in front of a storefront (WAF, Access, device detection) stays in Cloudflare at the edge, and Cloudflare's CDN cache in Conrad caching.
| Page | Covers | Questions |
|---|---|---|
| Workers and the runtime | Workers versus containers, isolates and cold starts, workerd and nodejs_compat, what fails on a Worker, service bindings, Snippets, Zero Trust | 7 |
| Storage and background work | KV, D1, R2, Durable Objects, Hyperdrive, Queues with dead letter queues and Workflows, and when to use which | 9 |
"Serverless functions that run in V8 isolates on Cloudflare's own runtime, workerd, in every one of its locations. An isolate starts in milliseconds inside an already running process, so there are practically no cold starts and no scaling to configure; the trade-off is limited memory and CPU time per request and no long-lived process. The runtime has web standard APIs and most of Node through nodejs_compat. Workers reach storage and other Workers through bindings: KV for global read-heavy data, D1 for SQL, R2 for files without egress fees, Durable Objects for consistent state, Hyperdrive for an existing Postgres, and Queues and Workflows for background work."
Nothing yet. Notes filed here show up on every page of this section.
Modules, plugins and layers
Module versus plugin, what a module can do with @nuxt/kit, build-time, app and Nitro hooks, an observability module with a provider option, layers and their override order, and when a platform ships a layer or a module.
Workers and the runtime
Workers versus containers, V8 isolates and why there are practically no cold starts, the workerd runtime and nodejs_compat, what cannot run on a Worker, service bindings, and Zero Trust instead of a VPN.