Cloudflare launches Workers Cache: a tiered caching layer in front of Worker entrypoints

Dan Lapid Connor Harwood

3h ago· 23 min readenNews

Summary

Cloudflare is launching Workers Cache, a tiered caching layer that sits in front of Worker entrypoints. When enabled, cacheable requests hit Cloudflare's cache first — if a fresh cached response exists, it's returned directly without running the Worker, saving CPU time and costs. On a cache miss, the Worker runs and if the response is cacheable, it's stored for subsequent requests. The system is configured via a single line of Wrangler config and standard Cache-Control headers, and is infinitely composable with regionally tiered caching.

Source

Hacker NewsCloudflare launches Workers Cache: a tiered caching layer in front of Worker entrypointsblog.cloudflare.com

Key quotes

· 5 pulled

When Workers Cache is enabled, every cacheable request to your Worker hits Cloudflare's cache first.

If there's a fresh cached response, Cloudflare returns it directly — your Worker doesn't run, and you don't pay CPU time for it.

On a miss, your Worker runs, and if your response is cacheable, Cloudflare stores it for the next request.

The next request from anywhere on Earth can be served from cache.

Infinitely composable, configured via standard HTTP headers

Snippet from the RSS feed

We are launching Workers Cache, a regionally tiered cache that sits directly in front of your Worker entrypoints. Infinitely composable, configured via standard HTTP headers

You might also wanna read

Workers - Requests made from Cloudflare Workers can now force a revalidation of their cache with the origin

Cloudflare·11mo ago

Cache - Smart Tiered Cache optimizes Load Balancing Pools

Cloudflare·1y ago

Workers - Bypass caching for subrequests made from Cloudflare Workers, with Request.cache

Cloudflare·1y ago

Comments

No comments yet. Be the first.