"use cache"s interaction with custom cache handlers

[gensc004]

The new "use cache" directive looks like it is going to solve a ton of scalability issues my team has had, in that it allows us to cache prerendered components separate from pages, and reuse them across multiple pages as they are being built.

After implementing it, I did notice that these cache's do not appear to leverage the custom cache handler we use to store cached data & pages in a Redis cluster. Is there any plans on having this new caching system use the custom cache handlers, and if not, is it something that I could contribute on?

[masterkain]

I'd like to know too, is "use cache" just in-memory?

[olek-es]

Looking at the documentation https://nextjs.org/docs/app/api-reference/directives/use-cache#use-cache-at-runtime, it says "cached in-memory" on the server :(

On the server, the cache entries of individual components or functions will be cached in-memory.

[magnusriga]

Any news on this? What happens when we revalidate a "use cache" entry, via tag from "cacheTag", if the app is running in several replicas in a docker swarm (or similar) cluster?

@gensc004 did you find out anything else?