As we know, for better or worse workers run in front of the CDN cache, but we do have the Cache API
As we know, for better or worse workers run in front of the CDN cache, but we do have the Cache API available within workers. So all requests will still hit the worker, but we can at least reduce load/cost on our database by checking the Cache API first.
However, assets cached via the Workers Cache API cannot be purged globally (local data centre only). This can only be done with cache tags available on an enterprise plan (https://developers.cloudflare.com/workers/reference/how-the-cache-works/#purge-assets-stored-with-the-cache-api).
So it is impossible to implement coordinated caching and invalidation with the Workers platform except for customers on a several hundred thousand $/yr enterprise plan. Is this intentional? And will it change?
However, assets cached via the Workers Cache API cannot be purged globally (local data centre only). This can only be done with cache tags available on an enterprise plan (https://developers.cloudflare.com/workers/reference/how-the-cache-works/#purge-assets-stored-with-the-cache-api).
So it is impossible to implement coordinated caching and invalidation with the Workers platform except for customers on a several hundred thousand $/yr enterprise plan. Is this intentional? And will it change?
Cloudflare Docs
How Workers interacts with the Cloudflare cache.
