docs: cacheHandlers (#85311)

Author: icyJoseph

docs/01-app/03-api-reference/01-directives/use-cache-private.mdx

@@ -7,6 +7,7 @@ related:
   links:
     - app/api-reference/directives/use-cache
     - app/api-reference/config/next-config-js/cacheComponents
+    - app/api-reference/config/next-config-js/cacheHandlers
     - app/api-reference/functions/cacheLife
     - app/api-reference/functions/cacheTag
     - app/guides/prefetching

docs/01-app/03-api-reference/01-directives/use-cache-remote.mdx

@@ -8,6 +8,7 @@ related:
     - app/api-reference/directives/use-cache
     - app/api-reference/directives/use-cache-private
     - app/api-reference/config/next-config-js/cacheComponents
+    - app/api-reference/config/next-config-js/cacheHandlers
     - app/api-reference/functions/cacheLife
     - app/api-reference/functions/cacheTag
     - app/api-reference/functions/connection

docs/01-app/03-api-reference/01-directives/use-cache.mdx

@@ -8,6 +8,7 @@ related:
     - app/api-reference/directives/use-cache-private
     - app/api-reference/config/next-config-js/cacheComponents
     - app/api-reference/config/next-config-js/cacheLife
+    - app/api-reference/config/next-config-js/cacheHandlers
     - app/api-reference/functions/cacheTag
     - app/api-reference/functions/cacheLife
     - app/api-reference/functions/revalidateTag
@@ -112,7 +113,7 @@ This means `use cache` cannot be used with [runtime data](/docs/app/getting-star
 
 ## `use cache` at runtime
 
-On the **server**, the cache entries of individual components or functions will be cached in-memory.
+On the **server**, the cache entries of individual components or functions will be cached in-memory by default. You can customize the cache storage by configuring [`cacheHandlers`](/docs/app/api-reference/config/next-config-js/cacheHandlers) in your `next.config.js` file.
 
 Then, on the **client**, any content returned from the server cache will be stored in the browser's memory for the duration of the session or until [revalidated](#during-revalidation).