mediumFrontend

What is request memoization in Next.js?

Q: What is request memoization in Next.js?

**TL;DR.** 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. layout fetch /u page fetch /u header fetch /u <path class='d-edge-accent' d='M142 76 H200' marker-end='url(#n

608 views

Understand the problem

Automatic deduping of identical fetches during one render.

nextjsrequest-memoizationfetchcaching

Attempt it yourself

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

Stuck? AI Nudge Available

Get a conceptual hint to guide your logic without spoiling the final implementation.

Study the solution

The solution is waiting

Give it an honest attempt first — then compare your thinking with the full walkthrough.

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 */ }

Join the discussion

Discussion (0)

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

What is Turbopack in Next.js and how does it compare to Webpack?

What is next.config.js in Next.js and what are common configurations?