Custom Next.js Cache Handler

You can configure the Next.js cache location if you want to persist cached pages and data to durable storage, or share the cache across multiple containers or instances of your Next.js application.

module.exports = {
  cacheHandler: require.resolve('./cache-handler.js'),
  cacheMaxMemorySize: 0, // disable default in-memory caching
}

View an example of a custom cache handler and learn more about the implementation.

API Reference

The cache handler can implement the following methods: get, set, revalidateTag, and resetRequestCache.

get()

Returns the cached value or null if not found.

set()

Returns Promise<void>.

revalidateTag()

Returns Promise<void>. Learn more about revalidating data or the revalidateTag() function.

resetRequestCache()

This method resets the temporary in-memory cache for a single request before the next request.

Returns void.

Good to know:

• revalidatePath is a convenience layer on top of cache tags. Calling revalidatePath will call your revalidateTag function, which you can then choose if you want to tag cache keys based on the path.

Platform Support

Learn how to configure ISR when self-hosting Next.js.

Version History