Is origin never hit regardless of user region when resource is in Cache Reserve?

Developers
1

For Workers & Pages, what is the name of the domain?

(general question)

What is the issue or error you’re encountering

I’m considering enabling cache reserve, but I need clarification on its behavior in the context of a global user base.

What steps have you taken to resolve the issue?

I’ve read the Cache Reserve documentation, but I’m still a bit unclear. To illustrate my question, let’s say I have enabled Cache Reserve. Now consider a user in Europe who first accesses a cacheable resource. As I understand, that resource will be fetched from the origin and then added to Cache Reserve. Now consider a user in Australia who accesses the same resource just after the European user. Will the Australian user get the cached resource?

I ask because with the regular tiered cache, the resource would need to be fetched from the origin again for the Australian user since Australia is a different region from Europe. So I’d like to know if that behavior is different with Cache Reserve enabled.

The docs seem to suggest that once a resource is in cache reserve - regardless of the location of the user who initially accessed it - it will be served from the cache for all subsequent requests within the TTL, regardless of user region. Is that correct?

Thanks for the clarification.

2

Yes, it indicates by the docs statement “Cache Reserve serves as the ultimate upper-tier cache” where the cached content store in a dedicated R2 storage.

1 Like
3

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.