Data Cache
The second Next.js caching tier: a server-side store of fetch results that persists across requests, users and deployments.
In more detail
In Next.js 15 fetch results are only stored when you opt in with cache: 'force-cache' or next.revalidate. Entries are refreshed after their revalidate time or invalidated on demand by tag or path.
Related terms
- Fetch API — The standard JavaScript function fetch() for making HTTP requests, built into browsers and current server runtimes, which returns a promise for the response.
- force-cache — The fetch option that tells Next.js to look in the Data Cache first and store the response there on a miss.
- cache tag — A label attached to cached data, such as products, so all entries with that label can be invalidated together.
- revalidation — Refreshing cached data or pages so they show new content, either after a time limit or on demand.
Taught in
- Request Memoization: Automatic Deduplication Tiers — Next.js 15 & Modern App Router Architecture
- Data Cache: Cross-Request Persistence & Fetch Tags — Next.js 15 & Modern App Router Architecture
- Full Route Cache: Static Rendering & Segment Config — Next.js 15 & Modern App Router Architecture