Skip to content

[Workers] Expliclity call out Cache Reserve incompatibility - WIP - DO NOT MERGE #17017

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

[Workers] Expliclity call out Cache Reserve incompatibility - WIP - DO NOT MERGE #17017

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
58c1069
[Workers]
markdembo Sep 23, 2024
1e31b7b
Add KV call out
markdembo Sep 23, 2024
145e28e
WIP for code example
markdembo Sep 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/content/docs/workers/reference/how-the-cache-works.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,10 +26,10 @@ Conceptually, there are two ways to interact with Cloudflare’s Cache using a W

* Caching responses generated by the Worker itself through `cache.put()`.

:::caution[Tiered caching]
:::caution[Tiered caching & Cache Reserve]


The Cache API is not compatible with tiered caching. To take advantage of tiered caching, use the [fetch API](/workers/runtime-apis/fetch/).
The Cache API is not compatible with tiered caching and Cache Reserve. To take advantage of tiered caching, use the [fetch API](/workers/runtime-apis/fetch/).


:::
Expand Down Expand Up @@ -118,7 +118,7 @@ This [template](/workers/examples/cache-api/) shows ways to use the cache API. F

:::caution[Tiered caching and the Cache API]

Cache API within Workers does not support tiered caching. Tiered Cache concentrates connections to origin servers so they come from a small number of data centers rather than the full set of network locations. Cache API is local to a data center, this means that `cache.match` does a lookup, `cache.put` stores a response, and `cache.delete` removes a stored response only in the cache of the data center that the Worker handling the request is in. Because these methods apply only to local cache, they will not work with tiered cache.
Cache API within Workers does not support tiered caching or use with Cache Reserve. Tiered Cache concentrates connections to origin servers so they come from a small number of data centers rather than the full set of network locations. Cache API is local to a data center, this means that `cache.match` does a lookup, `cache.put` stores a response, and `cache.delete` removes a stored response only in the cache of the data center that the Worker handling the request is in. Because these methods apply only to local cache, they will not work with tiered cache.
Copy link
Contributor

@irvinebroque irvinebroque Sep 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should tell people to use KV

:::

## Related resources
Expand Down