Data fetching in server components in NextJS - Step-by-Step Execution

Concept Flow - Data fetching in server components

Start Server Component Render

↓

Call async data fetching function

↓

Wait for data to be fetched

↓

Receive data

↓

Render component with data

↓

Send HTML to client

↓

End

The server component starts rendering, fetches data asynchronously, waits for it, then renders the UI with the data before sending HTML to the client.

Execution Sample

NextJS

export default async function Page() {
  const res = await fetch('https://api.example.com/data');
  const data = await res.json();
  return <div>{data.message}</div>;
}

This server component fetches data from an API, waits for the response, then renders a div showing the message from the data.

Execution Table

Step	Action	Evaluation	Result
1	Start rendering Page component	No data yet	Component begins execution
2	Call fetch('https://api.example.com/data')	Starts network request	Promise pending
3	Await fetch response	Wait for network	Response received
4	Call res.json()	Parse JSON body	Promise pending
5	Await res.json()	Wait for parsing	{"message":"Hello from API"}
6	Render <div>{data.message}</div>	Insert message into JSX	<div>Hello from API</div>
7	Send rendered HTML to client	HTML ready	Client receives <div>Hello from API</div>
8	End	Rendering complete	Server component finished

💡 Rendering ends after data is fetched and HTML is generated for the client.

Variable Tracker

Variable	Start	After Step 3	After Step 5	Final
res	undefined	Response object	Response object	Response object
data	undefined	undefined	{"message":"Hello from API"}	{"message":"Hello from API"}

Key Moments - 2 Insights

Why do we use 'await' before fetch and res.json()?

Because fetch and res.json() return promises that take time to complete. Using 'await' pauses execution until the data is ready, as shown in steps 3 and 5 of the execution table.

What happens if we try to render before data is fetched?

The component would not have the data to display, causing errors or empty content. The execution table shows rendering happens only after data is fetched (step 6).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'data' after step 3?

A Response object

B undefined

C {"message":"Hello from API"}

D Promise pending

💡 Hint

Check the 'data' variable in variable_tracker after step 3.

At which step does the component start rendering the HTML with the fetched data?

A Step 6

B Step 4

C Step 2

D Step 8

💡 Hint

Look at the 'Render

{data.message}

' action in the execution_table.

If the fetch call took longer, which step would be delayed?

A Step 1

B Step 6

C Step 3

D Step 8

💡 Hint

Step 3 is where the component waits for the fetch response.

Concept Snapshot

Data fetching in server components:
- Use async functions with await
- Fetch data before rendering
- Render UI with fetched data
- Server sends ready HTML to client
- No client-side loading needed

Full Transcript

In Next.js server components, data fetching happens during the server-side rendering process. The component function is async and uses await to pause execution until the fetch call completes and the JSON data is parsed. Once data is ready, the component renders JSX with the data included. The server then sends the fully rendered HTML to the client. This means the client receives content immediately without waiting for data loading. The execution table shows each step from starting the component, fetching data, parsing it, rendering, and sending HTML. Variables like 'res' and 'data' change as the fetch and parsing complete. Using await ensures the component waits for data before rendering, preventing errors or empty content.

Practice

1. What is the main advantage of fetching data inside Next.js server components?

easy

A. It requires no network requests at all.

B. Data is fetched before rendering, improving page speed and SEO.

C. It allows using React hooks like useState for data fetching.

D. Data fetching happens on the client side for faster UI updates.

Solution

1. Step 1: Understand server component data fetching

   Server components fetch data before rendering, so the page is ready with data when sent to the browser.

2. Step 2: Recognize benefits for speed and SEO

   This pre-rendering with data improves page load speed and helps search engines index content better.

3. Final Answer:

   Data is fetched before rendering, improving page speed and SEO. -> Option B

4. Quick Check:

   Server components fetch data early = D [OK]

Hint: Server components fetch data before render for speed and SEO [OK]

Common Mistakes:

• Thinking data fetching happens on client side in server components
• Confusing server components with client components
• Believing no network requests are needed

2. Which of the following is the correct way to fetch data inside a Next.js server component?

easy

A. const data = fetch('https://api.example.com/data', { method: 'POST' });

B. const data = fetch('https://api.example.com/data').then(res => res.json());

C. useEffect(() => { fetch('https://api.example.com/data'); }, []);

D. const data = await fetch('https://api.example.com/data');

Solution

1. Step 1: Identify server component data fetching syntax

   Server components support top-level await, so you can directly use await fetch().

2. Step 2: Check each option

   const data = await fetch('https://api.example.com/data'); uses await fetch correctly. const data = fetch('https://api.example.com/data').then(res => res.json()); assigns a Promise to data without awaiting. useEffect(() => { fetch('https://api.example.com/data'); }, []); uses useEffect, which is client-side only. const data = fetch('https://api.example.com/data', { method: 'POST' }); uses POST without context, likely incorrect for simple fetch.

3. Final Answer:

   const data = await fetch('https://api.example.com/data'); -> Option D

4. Quick Check:

   Top-level await fetch in server components = A [OK]

Hint: Use top-level await fetch() in server components [OK]

Common Mistakes:

• Using useEffect inside server components
• Not using await with fetch
• Confusing client-side hooks with server code

3. Given this server component code, what will be rendered?

export default async function Page() {
  const res = await fetch('https://api.example.com/user');
  const user = await res.json();
  return <h1>Hello, {user.name}!</h1>;
}

medium

A. <h1>Hello, John!</h1>

B. Error: fetch not allowed in server components

C. <h1>Hello, undefined!</h1>

D. Loading spinner until data arrives

Solution

1. Step 1: Understand server component data fetching

   The fetch call waits for the API response, then parses JSON to get user data.

2. Step 2: Render with fetched data

   The component returns an h1 element greeting the user by name, assuming user.name is 'John'.

3. Final Answer:

   <h1>Hello, John!</h1> -> Option A

4. Quick Check:

   Server component fetch + render data = C [OK]

Hint: Server components await fetch, render data directly [OK]

Common Mistakes:

• Expecting client-side loading states in server components
• Assuming fetch is disallowed in server components
• Not awaiting fetch response before rendering

4. Identify the error in this Next.js server component fetching data:

export default function Page() {
  const data = await fetch('https://api.example.com/data');
  return <div>Data loaded</div>;
}

medium

A. Missing JSON parsing of fetch response.

B. fetch is not allowed in server components.

C. Cannot use await inside a non-async function.

D. Return statement must be inside useEffect.

Solution

1. Step 1: Check function declaration

   The function is not marked async but uses await, which is invalid syntax.

2. Step 2: Understand correct usage

   To use await, the function must be async. fetch is allowed in server components, and JSON parsing is optional depending on usage.

3. Final Answer:

   Cannot use await inside a non-async function. -> Option C

4. Quick Check:

   await requires async function = A [OK]

Hint: Mark function async to use await inside it [OK]

Common Mistakes:

• Forgetting async keyword on server component
• Thinking fetch is disallowed in server components
• Misusing client hooks like useEffect in server components

5. You want to fetch user data and posts in a Next.js server component and display the user's name with the number of posts. Which code correctly fetches both and renders the result?

export default async function Page() {
  const userRes = await fetch('https://api.example.com/user');
  const postsRes = await fetch('https://api.example.com/posts');
  const user = await userRes.json();
  const posts = await postsRes.json();
  return <div>{user.name} has {posts.length} posts.</div>;
}

hard

A. Correctly fetches both and renders user name with posts count.

B. fetch calls must be inside useEffect for server components.

C. Cannot fetch multiple resources in one server component.

D. Must combine fetch calls with Promise.all to work.

Solution

1. Step 1: Analyze fetch calls in server component

   Server components support multiple await fetch calls sequentially as shown.

2. Step 2: Confirm rendering logic

   The component renders user.name and posts.length correctly after awaiting JSON parsing.

3. Final Answer:

   Correctly fetches both and renders user name with posts count. -> Option A

4. Quick Check:

   Multiple awaits in server component allowed = B [OK]

Hint: Await multiple fetches sequentially in async server component [OK]

Common Mistakes:

• Thinking useEffect is needed in server components
• Believing multiple fetch calls are disallowed
• Assuming Promise.all is required for correctness