Over-fetching and under-fetching problems in GraphQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is over-fetching in GraphQL?

Over-fetching happens when a query asks for more data than needed, causing extra information to be sent and slowing down the app.

beginner

What does under-fetching mean in GraphQL?

Under-fetching occurs when a query does not request enough data, so the app must make multiple requests to get all needed information.

beginner

How does GraphQL help solve over-fetching and under-fetching problems?

GraphQL lets clients ask exactly for the data they want, no more and no less, which avoids both over-fetching and under-fetching.

intermediate

Give an example of over-fetching in a REST API compared to GraphQL.

In REST, a user profile endpoint might return all user info even if the app only needs the name. In GraphQL, the query can ask just for the name, avoiding extra data.

intermediate

Why can under-fetching cause performance issues?

Under-fetching causes multiple network requests to get all needed data, which slows down the app and uses more resources.

What problem does over-fetching cause?

A Getting too much data than needed

B Getting too little data than needed

C No data returned

D Data format errors

Over-fetching means the query returns more data than the app actually needs.

Under-fetching leads to:

A Multiple requests to get all data

B One request with all data

C No data returned

D Faster app performance

Under-fetching means not enough data is returned, so the app must make more requests.

How does GraphQL prevent over-fetching?

A By returning all data always

B By limiting queries to one field

C By caching data on the server

D By letting clients specify exactly what data they want

GraphQL queries specify exactly which fields to return, avoiding extra data.

Which is a common cause of under-fetching?

A Requesting too many fields

B Using GraphQL

C Requesting too few fields

D Using REST APIs

Under-fetching happens when the query misses fields needed by the app.

What is a benefit of avoiding over-fetching and under-fetching?

A More network traffic

B Better app performance and user experience

C Slower app loading

D More server errors

Getting just the right data improves speed and user experience.

Explain over-fetching and under-fetching problems in simple terms.

Think about asking for too much or too little data.

How does GraphQL help fix over-fetching and under-fetching issues compared to REST APIs?

Focus on how GraphQL queries work.

Practice

1. What does over-fetching mean in GraphQL?

easy

A. Getting more data than the client actually needs

B. Getting less data than the client actually needs

C. Getting exactly the data the client requests

D. Getting data from multiple sources at once

Solution

1. Step 1: Understand the term over-fetching

   Over-fetching means the client receives more data than it requires, which can slow down the app.

2. Step 2: Compare with other options

   Under-fetching is the opposite (less data), exact fetching matches needs, and multiple sources is unrelated.

3. Final Answer:

   Getting more data than the client actually needs -> Option A

4. Quick Check:

   Over-fetching = More data than needed [OK]

Hint: Over-fetching means extra data beyond need [OK]

Common Mistakes:

• Confusing over-fetching with under-fetching
• Thinking over-fetching means exact data
• Mixing up data sources with data amount

2. Which GraphQL query syntax correctly avoids over-fetching by requesting only the user's name and email?

easy

A. { user { id name email } }

B. { user { name email posts } }

C. { user { name email } }

D. { user { id posts comments } }

Solution

1. Step 1: Identify requested fields

   { user { name email } } requests only name and email, exactly what is needed.

2. Step 2: Check other options for extra fields

   { user { id name email } } includes id (extra), B and D include posts and comments (extra data).

3. Final Answer:

   { user { name email } } -> Option C

4. Quick Check:

   Request only needed fields = { user { name email } } [OK]

Hint: Pick query with only needed fields, no extras [OK]

Common Mistakes:

• Including extra fields causing over-fetching
• Missing required fields causing under-fetching
• Confusing field names or nesting

3. Given this GraphQL query:

{ user { name posts { title } } }

What problem might this query cause if the client only needs the user's name?

medium

A. No problem, it fetches exactly what is needed

B. Under-fetching, missing the posts data

C. Syntax error due to missing fields

D. Over-fetching, fetching unnecessary posts data

Solution

1. Step 1: Analyze the query fields

   The query requests name and posts { title }, which includes posts data.

2. Step 2: Compare with client needs

   The client only needs name, so fetching posts is extra data causing over-fetching.

3. Final Answer:

   Over-fetching, fetching unnecessary posts data -> Option D

4. Quick Check:

   Extra fields cause over-fetching = Over-fetching, fetching unnecessary posts data [OK]

Hint: Check if query requests more than needed fields [OK]

Common Mistakes:

• Thinking missing posts is under-fetching
• Assuming no problem if query runs
• Confusing syntax errors with data issues

4. Identify the error in this GraphQL query that causes under-fetching:

{ user { name } }

The client needs the user's name and email.

medium

A. The query is missing the email field

B. The query has a syntax error in braces

C. The query requests too many fields

D. The query uses incorrect field names

Solution

1. Step 1: Check requested fields

   The query requests only name, missing email.

2. Step 2: Compare with client needs

   The client needs both name and email, so missing email causes under-fetching.

3. Final Answer:

   The query is missing the email field -> Option A

4. Quick Check:

   Missing needed fields = under-fetching [OK]

Hint: Check if all needed fields are requested [OK]

Common Mistakes:

• Assuming syntax error when none exists
• Thinking too many fields cause under-fetching
• Ignoring missing fields as a problem

5. You have a GraphQL query fetching a list of users with their posts and comments:

{ users { id name posts { title comments { text } } } }

To avoid over-fetching when the client only needs user names and post titles, how should you modify the query?

hard

A. { users { id name posts { title comments { text } } } }

B. { users { name posts { title } } }

C. { users { name posts { comments { text } } } }

D. { users { posts { title } } }

Solution

1. Step 1: Identify needed fields

   The client needs only name and post titles, no id or comments.

2. Step 2: Modify query to include only needed fields

   { users { name posts { title } } } requests name and posts { title }, exactly matching needs without extra data.

3. Final Answer:

   { users { name posts { title } } } -> Option B

4. Quick Check:

   Remove unneeded fields to avoid over-fetching [OK]

Hint: Keep only fields client needs, remove nested extras [OK]

Common Mistakes:

• Leaving comments in query causing over-fetching
• Removing needed fields like user name
• Removing posts entirely causing under-fetching