next-cache

What problem does it solve?

Next.js 15 caching presents four distinct layers and complex revalidation rules that often lead to stale data or over-fetching. This guide helps developers choose the right caching strategy to optimize data freshness and performance across applications.

Core Features & Use Cases

• Exposes and explains the four caches:
  • Request Memoization (in-memory, per render)
  • Data Cache (server-side, persistent)
  • Full Route Cache (server-side HTML cache)
  • Router Cache (client-side browser cache)
• Provides guidance on when to apply static content, ISR, or on-demand revalidation, including patterns for tag-based and path-based invalidation
• Real-world scenario: building a data-heavy Next.js app with frequently updated dashboards and product lists, applying proper revalidation to balance freshness, latency, and server load.

Quick Start

Determine the caching requirements for a given page, then apply the Next.js 15 caching layers with appropriate revalidation settings to meet freshness and performance goals.