Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Next.js
Next.jsmedium

App Router data fetching: what do `cache: 'no-store'` and `revalidate` change?

Tags
#nextjs#fetch#cache#revalidate
Back to categoryPractice quiz

Answer

`cache: 'no-store'` opts out of caching and always fetches fresh data. `revalidate` sets a TTL for cached data, enabling ISR‑like behavior where data is refreshed after N seconds. Both control how Next caches fetches on the server.

Related questions

Next.js
Static vs dynamic rendering in the App Router: what makes a route dynamic?
#nextjs#rendering#static
Next.js
`next/link` prefetching: what does it do and how can you control it?
#nextjs#link#prefetch
Next.js
Middleware in Next.js: what is it good for and what are its limitations?
#nextjs#middleware#edge
Next.js
Route Handlers in the App Router: how do you define them and what are they used for?
#nextjs#route-handlers#api
Next.js
Cache invalidation: what do `revalidatePath` and `revalidateTag` do?
#nextjs#cache#revalidate
Next.js
Dynamic routes: what does `generateStaticParams` do?
#nextjs#ssg#dynamic-routes