Learning path: domain to first edge API
Four progressive modules cover the request model, Worker development, verification, and Free-plan limits.
Edited and verified by Orange Book Editorial Team ·
This is a training plan with completion criteria, not a list of articles. Each module starts from an observable result produced by the previous one.
Path map
- 01Follow the request
Complete the request guide and explain proxying versus caching.
Start module - 02Run code
Start a minimal Worker locally and observe a real JSON response.
Start module - 03Finish a recipe
Add routing, headers, and an error branch; verify them with curl.
Start module - 04Understand constraints
Check Free-plan request, CPU, and bundle-size limits.
Review facts
Learning contract
What you will do
What you will not do yet
Completion criteria
Free-plan facts
Workers Free boundaries to know before finishing
Cloudflare can change plans and limits; reopen the primary source before implementation.
| Product / plan | Current fact | Scope and caveat |
|---|---|---|
| WorkersWorkers Free | Dynamic requests100,000 requests / day | Resets daily at 00:00 UTC; static asset requests are excluded. Verified · Source updated Primary source |
| WorkersWorkers Free | HTTP request CPU time10 ms / invocation | Time waiting on network, KV, or database I/O is not CPU time. Verified · Source updated Primary source |
| WorkersWorkers Free | Compressed Worker size3 MB (gzip) | Use the gzip size reported by a Wrangler dry run. Verified · Source updated Primary source |
A limit is not a performance target
A 10ms CPU limit does not mean each request should consume 10ms. Treat it as a design boundary and verify actual builds and requests.
End-of-path challenge
Add an invalid-path branch to the JSON API that returns a structured 404 response, then prove both success and error paths match expectations.
Next: open the JSON API recipe.
Primary sources
Did this page help you complete your goal?
Beta feedback is generated in this browser and is never uploaded automatically.
From a domain to your first complete application
Six verifiable stages cover domain setup, application development, data, defense, and production release.
Foundation layers for a complete Cloudflare application
Put static assets, request logic, structured data, object storage, and background work at the right boundaries.