If you self-host Next.js 15 on Docker, Kubernetes, Railway, Coolify, or Fly.io, you quickly run into two production caching challenges:
Multi-Instance Cache Desync : By default, Next.js stores ISR and App Router fetch caches on the local container filesystem/memory, meaning Pod A and Pod B serve inconsistent data after revalidateTag() .
The ISR Cache Stampede (Thundering Herd) : When a high-traffic cached route or query expires under 1,000 req/sec, dozens of concurrent requests trigger expensive regeneration queries against your database at the exact same millisecond.
To solve both problems with zero runtime dependencies in the core engine, we built KVDock — featuring a drop-in Next.js 15 Incremental Cache Handler, multi-tier L1/L2 caching, and single-flight stampede coalescing.
⚡ What Happens During a Cache Stampede?
Imagine a popular product page cache expires while 1,000 concurrent users load it simultaneously:
Metric Standard Uncoalesced Cache kvdock.getOrSet() (Single-Flight) Impact
Concurrent…