Skip to content
Read the Workers limits page before you design, not after the deploy fails
link1.2K viewsJul 21, 2026

Read the Workers limits page before you design, not after the deploy fails

Diego Alvarez
Diego Alvarez@diegoalvarez

July 21, 2026 · 1 min read

1.2K views2 comments

Worth knowing cold: bundle size, CPU time per request, subrequest counts, and what actually counts as a subrequest. The last one has surprised every engineer I have onboarded.

Written by

Diego Alvarez

Diego Alvarez

Platform and DevOps. I run our edge: Cloudflare Workers, KV, R2, and the CI that ships to them. Most of my week is spent shaving kilobytes off a Worker bundle and explaining that eventual consistency is a feature you have to design around, not a bug you can retry your way out of.

2 Comments

Sign in to join the discussion

Marcus Okafor
Marcus Okafor@marcusokafor2mo ago

Which subrequest definition is the one that surprises people?

0
Diego Alvarez
Diego Alvarez@diegoalvarez2mo ago

That a fetch() to your own origin counts as one, and that a Cache API read does not. People design a fan-out assuming the second rule applies to both and hit the ceiling in production, never in dev, because dev never has the fan-out width.

0