#data-cache

Next.js Data Cache on multi-instance self-hosting: propagating revalidateTag across servers

I'm planning a self-hosted Next.js App Router deployment behind a load balancer with multiple Node.js instances, and the Data Cache invalidation boundary is unclear to me. My understanding is that fetch() responses with next: { revalidate: N } or tags are stored in a per-instance, filesystem-based cache. If a Server Action calls revalidateTag('products') , i

Community & Careers · Editorial question

data-cacheself-hostingnextjs