Quick comparison
| Criterion | Cloudflare Workers | AWS Lambda | Comparability note |
|---|---|---|---|
| Primary compute duration | Cloudflare Workers30 seconds default; up to 5 minutesWorkers PaidCloudflare | AWS Lambda900 seconds (15 minutes)A function-level configuration ceiling; the configured timeout may be lower.Amazon Web Services | Active CPU milliseconds and wall-clock invocation duration are fundamentally different. |
| Memory | Cloudflare Workers128 MBFree and PaidCloudflare | AWS Lambda128 MB to 10,240 MBPer functionAmazon Web Services | Workers memory is per isolate; Lambda memory is configured per function environment. |
Which is best for your requirement?
Its documented primary compute duration scope fits your measured workload and the caveats shown in the comparison.
Its documented execution or account model better matches the exact requirement rather than a vendor-wide headline.
Test payload, duration, throughput, concurrency, failure behavior, billing scope, and recovery with representative traffic.
Validate the decision with your workload
Before choosing between Cloudflare Workers and AWS Lambda, reproduce the comparison with the exact plans, models, regions, runtimes, and invocation paths you intend to operate. The reviewed rows cover primary compute duration and memory; they do not turn different pricing, reliability, developer experience, or ecosystem tradeoffs into one universal score.
- Capture representative request sizes, token usage, duration, concurrency, storage, and failure behavior at realistic percentiles.
- Test the boundary and the recovery path on both candidates, including throttling, timeouts, partial failure, retries, and cost controls.
- Record which scoped observation drove the choice and recheck its official source before migration or a major traffic increase.