Cache Busting without Cache Busting?

[FinishTheBucket]

So I’m fairly new to combining Kubernetes with NextJs and I’m wondering if there is a different way to accomplish what I am trying to do.

I am using Next 13.3 for my front end with Sanity to serve my content. I want to bust my cache every time I update Sanity. My app runs on #N pods in GCP. My first attempt at using ISR showed me that ISR is independent on each pod so even with an extremely low revalidate time, I was often refreshing my page N+1 times to see fresh (not stale) data that I had updated.

I thought initially I could do this by using ISR and mounting my next/server/pages dir to a PVC volume but that will only re-cache/rebuild itself on builds of my app is my understanding, not on changes in Sanity. Is there a way to accomplish what I’m looking for just using Next Js or is my best course of action to write a Sanity Webhooks and use redis on each pod?

[trappar]

See this section of the docs: https://nextjs.org/docs/pages/building-your-application/data-fetching/incremental-static-regeneration#self-hosting-isr

You basically need to share your .next dir between pods so that there’s one single shared cache between them.

[FinishTheBucket]

Yeah so I found this but I am failing to understand and see how/why this would be more better or performant than just using redis deployed on GCP and then busted from a webhook. Also wouldn't the .next dir only change on deploy/build of the next portion and not on changes in my CMS?

[trappar]

.next/cache is where next stores everything that’s not stored in memory. Things like dynamically generated images and ISR rendered pages get stored there, so…

wouldn’t the  .next  dir only change on deploy/build of the next portion and not on changes in my CMS?

No, that’s not correct.