Over-fetching and under-fetching problems in GraphQL - Step-by-Step Execution

Concept Flow - Over-fetching and under-fetching problems

Client sends query

↓

Server receives query

↓

Server fetches data

↓

Fetch too much data?

Yes→Over-fetching problem

↓

Extra data sent

↓

Fetch too little data?

Yes→Under-fetching problem

↓

Missing data, client needs more queries

↓

Server sends response

↓

Client receives data

Client sends a query, server fetches data. If server fetches more than needed, it's over-fetching. If less, it's under-fetching, causing extra queries.

Execution Sample

GraphQL

query {
  user(id: 1) {
    id
    name
    posts {
      id
      title
    }
  }
}

Client requests user info with posts; server fetches user and posts data accordingly.

Execution Table

Step	Action	Data Requested	Data Fetched	Problem Detected	Result Sent
1	Client sends query	User id, name, posts (id, title)	N/A	N/A	N/A
2	Server processes query	User id, name, posts (id, title)	User id, name, posts (id, title, content)	Over-fetching	User id, name, posts (id, title, content)
3	Client receives data	User id, name, posts (id, title)	User id, name, posts (id, title, content)	Over-fetching	User id, name, posts (id, title, content)
4	Client sends query	User id, name	N/A	N/A	N/A
5	Server processes query	User id, name	User id	Under-fetching	User id
6	Client receives data	User id, name	User id	Under-fetching	User id
7	Client sends extra query for name	User name	User name	N/A	User name
8	Client receives extra data	User name	User name	N/A	User name

💡 Execution stops after client receives all requested data, possibly after multiple queries if under-fetching occurs.

Variable Tracker

Variable	Start	After Step 2	After Step 5	After Step 7	Final
Data Fetched	None	User id, name, posts (id, title, content)	User id	User id, name	User id, name, posts (id, title, content)

Key Moments - 2 Insights

Why does the server sometimes send more data than the client asked for?

Because the server fetches extra fields (like 'content' in posts) not requested, causing over-fetching as shown in step 2 and 3 of the execution_table.

Why does the client need to send multiple queries sometimes?

When the server fetches less data than requested (under-fetching), the client must send extra queries to get missing fields, as seen in steps 5 to 8.

Visual Quiz - 3 Questions

Look at the execution_table at step 2. What problem is detected?

A Under-fetching

B Over-fetching

C No problem

D Syntax error

💡 Hint

Check the 'Problem Detected' column at step 2 in the execution_table.

At which step does the client send an extra query due to under-fetching?

A Step 3

B Step 5

C Step 7

D Step 1

💡 Hint

Look for the step where the client sends an extra query after receiving incomplete data.

If the server fetched exactly the requested fields, how would the 'Data Fetched' value at step 2 change?

A It would match the requested fields exactly

B It would be empty

C It would include extra fields

D It would cause an error

💡 Hint

Compare 'Data Requested' and 'Data Fetched' columns at step 2 in the execution_table.

Concept Snapshot

Over-fetching: Server sends more data than client needs, wasting resources.
Under-fetching: Server sends less data, client must ask again.
GraphQL queries specify exactly what data is needed.
Proper server response avoids both problems.
Helps efficient data transfer and fewer requests.

Full Transcript

This visual execution shows how over-fetching and under-fetching happen in GraphQL. The client sends a query requesting specific fields. The server fetches data. If the server fetches extra fields not requested, it causes over-fetching, sending unnecessary data. If the server fetches fewer fields than requested, it causes under-fetching, forcing the client to send extra queries to get missing data. The execution table traces these steps, showing actions, data requested, data fetched, problems detected, and results sent. Variable tracking shows how fetched data changes over steps. Key moments clarify why extra data or extra queries happen. The quiz tests understanding of these steps. The snapshot summarizes the concept for quick review.