Cloudflare Workers
Serverless JavaScript and WebAssembly isolates that run on every Cloudflare data center.
- Provider
- cloudflare
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autoscaling | boolean | — | no | false | ▸ true |
| cpuTimeLimitMs | integer | — | no | 30000 | inherited |
| criticality | enum | low | medium | high | no | medium | inherited |
| instancePerEntity | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| memoryLimitMb | integer | — | no | 128 | inherited |
| ownsData | boolean | — | no | true | ▸ false |
| plan | enum | free | paid | no | free | inherited |
| runtime | string | — | no | — | ▸ javascript |
| shardingStrategy | enum | none | consistent-hash | range | lookup | no | none | inherited |
| singleWriter | boolean | — | no | false | inherited |
| smartPlacement | boolean | — | no | false | inherited |
| stateless | boolean | — | no | true | ▸ true |
| trigger | enum | fetch | cron | queue | email | no | — | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
A service that calls a third party synchronously, with no queue or workflow engine attached, has nowhere to park the request when the third party is slow or down. The failure becomes the user's problem instead of a retried job.
- — all of these hold:
- — the node has at least one synchronous outgoing edge to a third-party-api
- — this does not hold:
- — the node has at least one connected edge joining a workflow-engine or queue
Calling a worker synchronously puts the background job on the request path. The caller waits for the slowest part of the fan-out.
- — the node has at least one synchronous outgoing edge to a worker
A stateful service on a consistent hash ring needs something that owns the ring: detect a dead host, pick a replacement, tell everyone. Without a coordination service the ring is edited by hand during the outage.
- — all of these hold:
- — the node's `shardingStrategy` is "consistent-hash"
- — this does not hold:
- — the node has at least one connected edge joining a coordination-service
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "workers", component: "cloudflare-workers" }# yaml-language-server: $schema=../../schema/component.schema.json # Cloudflare Workers: serverless V8 isolates deployed to the whole network, scaled by the platform. # "Workers - Limits" gives the 30 s CPU default on paid plans; "Smart Placement" states requests run # in the data center nearest the client unless placement is configured. schemaVersion: "1" type: "component" id: "cloudflare-workers" kind: "app-server" provider: "cloudflare" docs: "https://developers.cloudflare.com/workers/platform/limits/" defaults: managed: true stateless: true autoscaling: true ownsData: false runtime: "javascript" properties: # Which handler the platform calls: fetch for HTTP, scheduled for Cron Triggers, queue for Queues # consumers, email for Email Routing ("Workers handlers"). No default. trigger: type: "enum" values: ["fetch", "cron", "queue", "email"] plan: type: "enum" values: ["free", "paid"] default: "free" cpuTimeLimitMs: type: "integer" default: 30000 smartPlacement: type: "boolean" default: false memoryLimitMb: type: "integer" default: 128