Your Worker can now have its own cache in front of it
Cloudflare launched Workers Cache, a tiered cache that sits in front of your Worker, enabled by a single line in wrangler.jsonc (`"cache": { "enabled": true }`). On a cache hit, the Worker does not run and CPU time is not billed; on a miss, the Worker runs and populates the cache. It supports stale-while-revalidate, Vary-based content negotiation, and multi-tenant isolation via ctx.props. Unlike zone-level caches, Workers Cache belongs to the Worker itself, working on custom domains, workers.dev, and Workers for Platforms. Most notably, the cache sits in front of every Worker entrypoint, including those invoked via service bindings and ctx.exports, enabling developers to compose an app as a chain of entrypoints with per-entrypoint caching control. Framework integrations (including Astro) are available.