Next.js · Senior · Question 5 of 75
What do you need to consider when self-hosting Next.js on several Kubernetes pods?
- ✓Correct answer: The cache is local to each instance by default; you need a shared cache handler
- 2Nothing: instances sync their cache with each other automatically
- 3You must disable ISR - it works only on Vercel
Explanation
By default, generated pages and data are stored in each pod's memory and disk. Without shared storage, revalidateTag on one pod doesn't invalidate the cache on others, and users see different versions. You should also configure deploymentId to protect against version skew during rolling updates.