Full support for Cache Components
Our own server runs your build through the Next.js Adapter API. 'use cache' entries live in a shared Redis, so every instance sees the same cache. When you call revalidateTag, we purge exactly the URLs that used that tag from the CDN. Hashed assets of every deployment are kept, so open tabs never break after a deploy.
async function Products() { 'use cache' cacheLife('hours') cacheTag('catalog') // revalidateTag('catalog') → those pages purged at the edge }