Why data fetching differs in Next.js - Visual Breakdown

Concept Flow - Why data fetching differs in Next.js

Start: User requests page

↓

Is page a Server Component?

No→Client Component fetches data on client

Yes↓

Server Component fetches data on server

↓

Render page with fetched data

↓

Send HTML to browser

↓

Browser hydrates page

↓

Client-side interactivity continues

Next.js fetches data differently depending on whether the component runs on the server or client, affecting when and where data is loaded.

Execution Sample

NextJS

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

This Server Component fetches data on the server before rendering the page.

Execution Table

Step	Action	Location	Result	Effect
1	User requests page	Browser	Request sent to Next.js server	Start data fetching process
2	Page component runs	Server	fetch() called	Data requested from API
3	Await fetch response	Server	Data received	Data ready for rendering
4	Parse JSON	Server	JSON parsed	Data accessible as object
5	Render JSX with data	Server	<div>message</div>	HTML generated with data
6	Send HTML to browser	Server -> Browser	HTML received	Page visible with data
7	Browser hydrates page	Browser	React attaches events	Page interactive
8	User interacts	Browser	Client-side code runs	Dynamic updates possible
9	If Client Component fetches data	Browser	fetch() called on client	Data fetched after page load
10	Exit	N/A	No more server fetch	Data fetching complete

💡 Data fetching ends after server renders or client fetches depending on component type

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
data	undefined	Promise pending	Response object	Response object	Response object
json	undefined	undefined	undefined	Parsed JSON object	Parsed JSON object

Key Moments - 3 Insights

Why does data fetching happen on the server in Server Components?

Because Server Components run on the server, they can fetch data before sending HTML to the browser, as shown in execution_table steps 2-6.

What happens if data fetching is done in a Client Component?

Data fetching occurs in the browser after the page loads, causing a delay in showing data, as seen in execution_table step 9.

Why is hydration important after server-side rendering?

Hydration attaches React's event handlers to the static HTML so the page becomes interactive, explained in execution_table step 7.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the server receive the data from the API?

A Step 3

B Step 5

C Step 7

D Step 9

💡 Hint

Check the 'Result' column for when 'Data received' happens on the server.

According to the variable tracker, when is the JSON data parsed?

A After Step 2

B After Step 3

C After Step 4

D Final

💡 Hint

Look at the 'json' variable value changes in the variable_tracker table.

If the page used only Client Components for data fetching, when would fetch() be called?

A Step 2

B Step 5

C Step 7

D Step 9

💡 Hint

Refer to execution_table step describing client-side fetch.

Concept Snapshot

Next.js data fetching differs by component type:
- Server Components fetch data on the server before rendering.
- Client Components fetch data in the browser after page load.
- Server fetching sends ready HTML to browser.
- Client fetching delays data display until after hydration.
- Hydration makes server-rendered pages interactive.

Full Transcript

When a user requests a Next.js page, the framework checks if the page uses Server Components or Client Components. Server Components run on the server and fetch data before rendering HTML. This means the user receives a fully rendered page with data already included. The browser then hydrates the page to add interactivity. If the page uses Client Components for data fetching, the browser fetches data after loading the page, causing a delay before data appears. This difference affects user experience and performance. The execution table shows each step from request to rendering and hydration, while the variable tracker follows data variables through the process. Key moments clarify why server fetching happens early and client fetching happens later. The quiz tests understanding of when data is fetched and parsed.

Practice

1. Why does Next.js use different methods for data fetching?

easy

A. Because Next.js only works with static data

B. Because Next.js does not support client-side data fetching

C. Because all data must be fetched only on the server

D. Because data can be fetched at different times for better performance

Solution

1. Step 1: Understand data fetching timing in Next.js

   Next.js allows fetching data before the page loads (server-side or static) or after the page loads (client-side).

2. Step 2: Recognize the reason for multiple methods

   Using different methods helps improve performance and user experience by choosing the best time to fetch data.

3. Final Answer:

   Because data can be fetched at different times for better performance -> Option D

4. Quick Check:

   Data fetching timing = A [OK]

Hint: Think when data is needed: before or after page loads [OK]

Common Mistakes:

• Assuming Next.js only fetches data on the server
• Believing client-side fetching is not supported
• Thinking all data must be static

2. Which of the following is the correct way to fetch data at build time in Next.js?

easy

A. export async function getStaticProps() { return { props: {} } }

B. export async function getServerSideProps() { return { props: {} } }

C. export async function fetchData() { return { props: {} } }

D. export async function getClientSideProps() { return { props: {} } }

Solution

1. Step 1: Identify build-time data fetching method

   Next.js uses getStaticProps to fetch data at build time for static generation.

2. Step 2: Compare options with Next.js conventions

   getServerSideProps is for server-side rendering, not build time; others are invalid function names.

3. Final Answer:

   export async function getStaticProps() { return { props: {} } } -> Option A

4. Quick Check:

   Build-time fetch = getStaticProps A [OK]

Hint: Remember: Static = getStaticProps, Server = getServerSideProps [OK]

Common Mistakes:

• Confusing getServerSideProps with getStaticProps
• Using incorrect function names
• Thinking client-side fetching uses special props functions

3. What will be the rendered output if you use getServerSideProps to fetch data that changes every second?

medium

A. The page shows the data as it was at build time

B. The page never updates after first load

C. The page shows the latest data on every request

D. The page shows an error because data changes too fast

Solution

1. Step 1: Understand getServerSideProps behavior

   This function runs on every request, so it fetches fresh data each time the page loads.

2. Step 2: Apply to data changing every second

   Since data changes frequently, getServerSideProps ensures the page always shows the latest data.

3. Final Answer:

   The page shows the latest data on every request -> Option C

4. Quick Check:

   Server-side fetch = fresh data B [OK]

Hint: Server-side fetch updates on every request [OK]

Common Mistakes:

• Thinking getServerSideProps caches data at build time
• Assuming data never updates after first load
• Believing it causes errors with fast-changing data

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

export async function getStaticProps() {
  const res = await fetch('https://api.example.com/data')
  const data = await res.json()
  return { data }
}

medium

A. Missing return of props object wrapping data

B. fetch cannot be used inside getStaticProps

C. Async functions are not allowed in Next.js data fetching

D. The URL must be relative, not absolute

Solution

1. Step 1: Check return value format in getStaticProps

   Next.js expects an object with a props key containing the data, not just data alone.

2. Step 2: Identify the missing wrapper

   The code returns { data } but should return { props: { data } } for Next.js to pass props correctly.

3. Final Answer:

   Missing return of props object wrapping data -> Option A

4. Quick Check:

   Return props object = C [OK]

Hint: Always return { props: { ... } } in getStaticProps [OK]

Common Mistakes:

• Returning data directly without props wrapper
• Thinking fetch is disallowed in getStaticProps
• Believing async functions are forbidden

5. You want to show user-specific data that updates frequently but also want fast initial page load in Next.js. Which approach best fits this need?

hard

A. Use getStaticProps to fetch data and revalidate every second

B. Use getStaticProps for static data and fetch user data client-side after load

C. Fetch all data client-side only after page loads

D. Use getServerSideProps to fetch data on every request

Solution

1. Step 1: Analyze requirements for fast initial load and frequent updates

   Static data can be fetched at build time for fast load; user-specific data changes often and should be fetched client-side.

2. Step 2: Evaluate options

   Use getStaticProps to fetch data and revalidate every second revalidates too frequently and may cause performance issues; Use getServerSideProps to fetch data on every request delays initial load; Fetch all data client-side only after page loads delays all data; Use getStaticProps for static data and fetch user data client-side after load balances fast load and fresh user data.

3. Final Answer:

   Use getStaticProps for static data and fetch user data client-side after load -> Option B

4. Quick Check:

   Static + client fetch = D [OK]

Hint: Combine static build with client fetch for user data [OK]

Common Mistakes:

• Using only server-side fetching causing slow load
• Fetching everything client-side causing blank initial page
• Overusing revalidation causing unnecessary server load