Setting the file. One moment.
Subchapter 7.53
references/support-topics/runtime-cache-reusable-data.mdMarkdown1 KBView on GitHub
Runtime Cache is only useful when the same server-side result is reused across requests. Treat it as a measured alternative when CDN response caching is unsafe or incomplete.
Use p75/p95 latency, call count, caller routes, and transfer bytes. In source, identify database queries, external API calls, or expensive computations that return the same result for many viewers.
Skip per-user data, mutations, secrets, one-off requests, or unknown freshness. Skip Runtime Cache when CDN caching solves the route. For Next with Cache Components, check use cache: remote first; use Runtime Cache only as a justified fallback.
Name the reusable data, observed route or hostname pressure, required freshness window, and the exact call site to wrap.