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.

Good to know: ThecacheHandler (singular) configuration is specifically used by Next.js for server cache operations such as storing and revalidating ISR and route handler responses. It isnot used by'use cache' directives. For'use cache' directives, usecacheHandlers (plural) instead.

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

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

API Reference

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

get()

Returns the cached value ornull if not found.

set()

ReturnsPromise<void>.

revalidateTag()

ReturnsPromise<void>. Learn more aboutrevalidating data or therevalidateTag() function.

resetRequestCache()

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

Returnsvoid.

Good to know:

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

Platform Support

Learn how toconfigure ISR when self-hosting Next.js.

Version History