Workers Cache
Points and comments are a snapshot, not live.
Cloudflare launches Workers Cache, a tiered cache in front of Workers, configured via code.
Workers Cache places a tiered cache in front of Workers, serving cached responses without invoking the Worker. It is enabled by a single Wrangler config line and uses standard `Cache-Control` headers, including `stale-while-revalidate` for served-stale-while-refreshing. The cache supports `Vary` for content negotiation, cache tags for programmatic purging, and is scoped per Worker, not per zone. Tiered caching is free and default. Available today on all plans.
What commenters are saying
Commenters broadly welcome the feature, calling it exactly what Workers needed, especially for server-rendered apps where Workers previously ran on every request before caching. Several note the sensible adherence to the HTTP spec with `Cache-Control` and `stale-while-revalidate`. Many express frustration with the article's writing style, suspecting LLM authorship due to excessive hyphenated phrases, em dashes, and a formulaic structure. Some question why it took nine years to implement; others point to equivalent solutions like CloudFront for AWS Lambda.