Request memoization in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is request memoization in Next.js?

Request memoization is a technique to save the result of a server request so that if the same request happens again, Next.js can reuse the saved result instead of running the request again. This makes the app faster and uses less server work.

beginner

How does request memoization improve performance in Next.js apps?

By saving the results of server requests, Next.js avoids repeating the same work. This means pages load faster because data is ready to use without waiting for the server to fetch it again.

intermediate

Which Next.js feature helps implement request memoization easily?

Next.js uses React Server Components and caching hooks like 'cache' from 'react' to memoize requests. This means you can wrap your data fetching functions to remember their results automatically.

beginner

What happens if you don’t use request memoization for repeated data fetching in Next.js?

Without memoization, the server fetches the same data every time a request happens. This slows down the app and uses more server resources, making the user wait longer.

intermediate

How can you manually memoize a fetch request in Next.js using React's cache?

You can wrap your fetch function with React's 'cache' function like this: const memoizedFetch = cache(async (url) => { const res = await fetch(url); return res.json(); }); This saves the result for each URL so repeated calls reuse data.

What is the main benefit of request memoization in Next.js?

A Faster page loads by reusing data

B Adding more server requests

C Making the app use more memory

D Disabling caching completely

Request memoization saves data from previous requests so Next.js can reuse it, making pages load faster.

Which React feature is commonly used for request memoization in Next.js?

A cache

B useState

C useEffect

D useRef

React's 'cache' function helps memoize async functions like data fetching in Next.js.

What happens if you fetch the same data multiple times without memoization?

A The app runs faster

B The data is saved automatically

C The server does extra work each time

D The data is deleted

Without memoization, the server fetches data again and again, causing extra work and slower responses.

In Next.js, where is request memoization most useful?

A In client-side only components

B In server components fetching data

C In CSS styling

D In static HTML files

Request memoization is mainly used in server components where data fetching happens.

Which of these is NOT a benefit of request memoization?

A Better user experience

B Faster data access

C Reduced server load

D Increased repeated fetches

Request memoization reduces repeated fetches, it does not increase them.

Explain request memoization in Next.js and why it matters for app performance.

Think about how saving answers helps avoid repeating the same question.

Describe how you would use React's cache function to memoize a data fetch in a Next.js server component.

Imagine putting fetched data in a safe box to open again without fetching.

Practice

1. What is the main purpose of request memoization in Next.js?

easy

A. To increase the number of server requests

B. To save repeated fetches by remembering previous results

C. To disable caching for all requests

D. To make fetch requests slower

Solution

1. Step 1: Understand request memoization concept

   Request memoization stores the results of previous fetches to avoid repeating the same network calls.

2. Step 2: Identify the effect on performance

   By remembering previous results, it reduces server load and speeds up response times.

3. Final Answer:

   To save repeated fetches by remembering previous results -> Option B

4. Quick Check:

   Request memoization = Save repeated fetches [OK]

Hint: Memoization means remembering past results to avoid repeats [OK]

Common Mistakes:

• Thinking memoization increases server requests
• Confusing memoization with disabling cache
• Assuming memoization slows down fetches

2. Which of the following is the correct way to memoize a fetch function in Next.js using the built-in cache?

easy

A. const cachedFetch = fetch.cache('/api/data')

B. const cachedFetch = async cache(() => fetch('/api/data'))

C. const cachedFetch = cache(async () => await fetch('/api/data'))

D. const cachedFetch = cache.fetch('/api/data')

Solution

1. Step 1: Recall Next.js cache usage

   Next.js provides a cache function that wraps async functions to memoize their results.

2. Step 2: Check correct syntax

   The correct syntax is cache(async () => await fetch(...)), which matches const cachedFetch = cache(async () => await fetch('/api/data')).

3. Final Answer:

   const cachedFetch = cache(async () => await fetch('/api/data')) -> Option C

4. Quick Check:

   cache wraps async fetch function = const cachedFetch = cache(async () => await fetch('/api/data')) [OK]

Hint: Use cache() to wrap async fetch functions correctly [OK]

Common Mistakes:

• Placing cache inside async incorrectly
• Using non-existent fetch.cache method
• Calling cache.fetch which does not exist

3. Given this code snippet in Next.js, what will be logged on the second call to getData()?

import { cache } from 'react';

const getData = cache(async () => {
  console.log('Fetching data');
  return await fetch('/api/data').then(res => res.json());
});

await getData();
await getData();

medium

A. Fetching data

B. Fetching data
Fetching data

C. No output

D. Error: cache is not a function

Solution

1. Step 1: Understand cache behavior on repeated calls

   The cache function memoizes the async function result, so the fetch and console.log run only once.

2. Step 2: Analyze the second call effect

   On the second call, the cached result is returned without running the function body again, so no console.log output.

3. Final Answer:

   Fetching data -> Option A

4. Quick Check:

   cache memoizes, so console.log runs once [OK]

Hint: cache runs function once, returns cached result later [OK]

Common Mistakes:

• Expecting console.log to run twice
• Thinking cache disables function execution
• Confusing cache with normal fetch calls

4. Identify the error in this Next.js memoized fetch code:

import { cache } from 'react';

const getData = async cache(() => {
  return await fetch('/api/data').then(res => res.json());
});

medium

A. TypeError: cache is not a function

B. RuntimeError: fetch is not defined

C. No error, code works fine

D. SyntaxError: 'cache' must wrap the async function, not be called inside it

Solution

1. Step 1: Check cache usage syntax

   The cache function must wrap the async function, not be called inside the async declaration.

2. Step 2: Identify the syntax mistake

   Writing async cache(() => ...) is invalid syntax; it should be cache(async () => ...).

3. Final Answer:

   SyntaxError: 'cache' must wrap the async function, not be called inside it -> Option D

4. Quick Check:

   cache wraps async function syntax = SyntaxError: 'cache' must wrap the async function, not be called inside it [OK]

Hint: cache wraps async function, not inside async declaration [OK]

Common Mistakes:

• Placing async before cache call incorrectly
• Assuming fetch is undefined without context
• Thinking cache is not imported

5. You want to memoize a fetch function in Next.js that depends on a dynamic URL parameter. Which approach correctly memoizes requests per unique URL?

hard

A. Use cache with a function that takes the URL as argument and memoizes internally

B. Use a single cached function without parameters for all URLs

C. Memoize only the first URL and ignore others

D. Do not use cache; fetch every time for dynamic URLs

Solution

1. Step 1: Understand memoization with parameters

   To memoize requests per unique URL, the cache must consider the URL argument to store separate results.

2. Step 2: Use cache with parameterized function

   Wrapping a function that takes URL as input with cache memoizes each unique URL separately.

3. Final Answer:

   Use cache with a function that takes the URL as argument and memoizes internally -> Option A

4. Quick Check:

   cache with parameters memoizes per input [OK]

Hint: Memoize functions with parameters to cache per input [OK]

Common Mistakes:

• Using single cache for all URLs causing wrong data
• Ignoring memoization for dynamic inputs
• Assuming cache disables dynamic fetching