Don't Go South With Next.js Caching – Supercharging Performance
summary
Next.js 15 defaults to no caching and fetch supports force-cache, no-store, revalidate <seconds> so pick per-route behavior not the hype. Server components can cache SQL results with unstable_cache and on-demand invalidation uses revalidatePath / revalidateTag — forgetting tags is a common bug. Middleware or cookies can bust CDN/ISR caches because headers change; ISR is eventual, not real-time. Debug with next build --debug and prefer no-store for always-fresh endpoints.
AI-written summary · about
chapters (9)
- 0:00Introduction to caching
- 1:26Why caching matters
- 3:54Next.js 15 caching overview
- 7:07Understanding cache pyramid
- 8:56Caching in app router
- 11:02Common caching mistakes
- 12:47Middleware impact on caching
- 13:52Supercharging caching tips
- 14:37Final thoughts and Q&A
related talks
24mCache for Commerce Performance and Optimization for High Volume Sales
37mHands On: How To Migrate To 16 and "Use Cache"
30mComposition, Caching, and Architecture in modern
16mHigh-speed personalization with Next.js
08mAdvanced SSR Caching with React
25mCaching strategies on https://dev.to
29mLove your cache: Optimize for the second load
25mNext.js: Choosing an Optimal Rendering Pattern for your Application