@cloudflare/next-on-pages comes with support for data revalidation and caching for fetch requests. This is done in our router and acts as an extension to Next.js' built-in functionality.
Caching in Next.js applications (thus applications built using @cloudflare/next-on-pages as well) is enabled by default. If you wish to opt-out of this caching please refer to the official Next.js documentation.
Also please note that the cache is persisted across deployments, again inline with what the Next.js documented behavior. You are responsible for revalidating/purging this cache. It is not handled for you by @cloudflare/next-on-pages or Cloudflare Pages.
There are currently two different storage options that @cloudflare/next-on-pages supports, the Cache API and Workers KV.
In the future, support will be available for creating custom cache interfaces and using different bindings.
The Cache API is a per data-center cache that is ideal for storing data that is not required to be accessible globally.
It is worth noting that Vercel's Data Cache is regional (and not global) the same applies to Workers Cache API, so with this storage option there is no difference in terms of data availability. This includes cache related operations such as the Next.js' on-demand revalidation.
Workers KV is a low-latency key-value store that is ideal for storing data that should be globally distributed. KV is eventually consistent, which means that it will take up to 60 seconds for updates to be reflected globally.
It is important to note that, contrary to the Vercel Data Cache and Workers Cache API, the KV storage is global (and not regional), this naturally changes the data availability and the effect of operations such as the on-demand revalidation.
To use Workers KV for caching all you need to do is to add a KV binding (as documented in the Cloudflare Pages documentation) to your Pages project with the name __NEXT_ON_PAGES__KV_SUSPENSE_CACHE.
Important
The Workers KV storage solution is, compared to the Cache API, less surprising but still equally performant. It adds the extra benefits of being able to easily inspect the cache content and easily invalidate/purge it (in the case of production cache via the Dashboard KV UI).
So for the above reasons the Workers KV storage solution is the one we recommend.