Your Worker can now have its own cache in front of it
- Source
- blog.cloudflare.com
- Author
- Cloudflare
- Date
If you're running server-rendered apps or backends on Cloudflare Workers, this lets cache hits skip Worker execution (and its CPU billing) entirely using just standard Cache-Control headers and Wrangler config — no need for a separate CDN layer or build-time prerendering to get near-static edge performance.
- AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
“On a cache hit, your Worker doesn't run at all. Cloudflare returns the cached response and your CPU billing stays at zero.”
“Workers stopped being a thing you bolted onto an origin and started being the origin.”
“You get the speed of a static site without the build time, and the freshness of server rendering without the cost.”
“We don't know of another platform that gives you a cache that sits inside a single deployable unit, between the parts of your application, with each cache stage configured by the code on either side of it.”
postCloudflare AI Search goes GA with image embeddings and PDF OCR
articleWe are introducing Clef and Clef-flash, open-source decision models hosted on…
articleToday, we’re making the Cloudflare Monetization Gateway available as part of a…
articleCloudflare Auto Router picks cheaper models per request in AI Gateway
Checking sign-in…
Loading comments…