Automatic deduping of identical fetches during one render.
Skip to solutionKEEP THE
mediumFrontend
What is request memoization in Next.js?
608 views
01
Understand the problem
nextjsrequest-memoizationfetchcaching
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
Within a single server render, Next.js memoizes identical fetch() calls (same URL/options) so multiple components requesting the same data trigger only one network call. This lets you fetch where you need data without prop-drilling or manual deduping.
Solution ready — 2 min read
Classified // press E to declassify
04
Read the code
Colocated fetches deduped; cache() for DB
// Both call getUser() in the same render → one DB query
import { cache } from 'react';
export const getUser = cache(async (id: string) => db.user.find(id));
// layout.tsx and page.tsx can each await getUser(id) freely — deduped.
async function Layout({ params }) { const u = await getUser(params.id); /* ... */ }
async function Page({ params }) { const u = await getUser(params.id); /* same, cached */ }05
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 46 of 95 decoded in the Next.js track. One more won't hurt.