Skip to solution
hardFrontend

unstable_cache vs `cache` (React) — which dedupes what?

220 views
01

Understand the problem

unstable_cache is Next's persistent Data Cache; cache from React is per-request memoization — they stack.

cachingunstable_cache
02

Attempt it yourself

Sketch your approach before reading the solution — that's what interviews test.

Nudge consolestandby

Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.

03

Study the solution

cache() (React) memoizes per request; unstable_cache (Next) persists across requests with tags/revalidate — use cache to dedupe, unstable_cache to persist, or 'use cache' to replace the latter.

<marker id="a" viewBox="0 0

Solution ready — 2 min read

Classified // press E to declassify

04

Join the discussion

Discussion (0)

Sign in to join the discussion.

No responses yet. Be the first to share what you think.

Transmission complete // awaiting log

KEEP THE
STREAK ALIVE.

Dossier 91 of 95 decoded in the Next.js track. One more won't hurt.

Back to track