Why GraphQL exists - Quick Recap

Recall & Review

beginner

What problem does GraphQL solve compared to traditional REST APIs?

GraphQL solves the problem of over-fetching and under-fetching data by allowing clients to request exactly what they need in a single query.

beginner

How does GraphQL improve efficiency in data retrieval?

GraphQL lets clients specify the exact fields they want, reducing unnecessary data transfer and multiple requests.

intermediate

Why is flexibility important in GraphQL's design?

Flexibility allows clients to evolve their data needs without changing the backend, making development faster and easier.

intermediate

What is a common limitation of REST APIs that GraphQL addresses?

REST APIs often require multiple endpoints and requests to gather related data, while GraphQL can fetch all related data in one query.

intermediate

How does GraphQL help frontend and backend teams work better together?

GraphQL creates a clear contract where frontend can ask for data independently, reducing backend changes and speeding up development.

What is a main reason GraphQL was created?

A To make APIs slower but more secure

B To replace databases entirely

C To allow clients to request only the data they need

D To remove the need for servers

GraphQL was created to let clients specify exactly what data they want, avoiding over-fetching or under-fetching.

How does GraphQL reduce the number of requests compared to REST?

A By limiting data to only one field

B By caching all data on the client

C By using multiple endpoints for each data type

D By combining multiple data requests into a single query

GraphQL allows clients to request all needed data in one query, reducing multiple round trips.

Which of these is NOT a benefit of GraphQL?

A Automatic database indexing

B Flexible queries

C Single endpoint for all queries

D Exact data fetching

GraphQL does not handle database indexing; it focuses on flexible data querying.

Why might frontend developers prefer GraphQL?

A They can get exactly the data they want without backend changes

B They don't need to write any queries

C GraphQL automatically generates UI components

D It requires no knowledge of data structure

GraphQL lets frontend developers request data precisely, reducing dependency on backend changes.

What is a key difference between REST and GraphQL?

A REST is only for mobile apps; GraphQL is for web apps

B REST uses multiple endpoints; GraphQL uses a single endpoint

C REST requires no server; GraphQL requires no client

D REST is a database; GraphQL is a programming language

REST APIs typically have many endpoints, while GraphQL uses one endpoint for all queries.

Explain in simple terms why GraphQL was created and what problems it solves.

Think about how apps get data and what can be annoying about old ways.

Describe how GraphQL helps frontend and backend teams work more smoothly together.

Focus on teamwork and communication between developers.

Practice

1. Why was GraphQL created as a new way to request data from APIs?

easy

A. To force clients to download all data every time.

B. To make APIs slower and more complex.

C. To let clients ask for exactly the data they need, no more, no less.

D. To replace databases with a new storage system.

Solution

1. Step 1: Understand the problem GraphQL solves

   Traditional APIs often send too much or too little data, causing inefficiency.

2. Step 2: Identify GraphQL's main benefit

   GraphQL allows clients to specify exactly what data they want, improving efficiency.

3. Final Answer:

   To let clients ask for exactly the data they need, no more, no less. -> Option C

4. Quick Check:

   GraphQL = precise data requests [OK]

Hint: GraphQL lets you ask only for what you need [OK]

Common Mistakes:

• Thinking GraphQL makes APIs slower
• Believing GraphQL replaces databases
• Assuming GraphQL sends all data always

2. Which of the following is the correct way to request a user's name and email in GraphQL?

easy

A. query { user name email }

B. query { user { name, email } }

C. query user { name, email }

D. query { user: name, email }

Solution

1. Step 1: Recall GraphQL query syntax

   GraphQL queries use curly braces to specify fields inside objects.

2. Step 2: Check each option's syntax

   query { user { name, email } } correctly nests fields inside user with commas separating fields.

3. Final Answer:

   query { user { name, email } } -> Option B

4. Quick Check:

   Correct GraphQL query syntax = query { user { name, email } } [OK]

Hint: Fields inside braces, separated by commas [OK]

Common Mistakes:

• Missing braces around nested fields
• Using colons incorrectly in queries
• Omitting commas between fields

3. Given this GraphQL query:
query { book(id: "1") { title author { name } } }
What data will the client receive?

medium

A. { "book": { "title": "1984", "author": { "name": "George Orwell" } } }

B. { "book": { "title": "1984" } }

C. { "title": "1984", "author": "George Orwell" }

D. { "book": { "name": "George Orwell" } }

Solution

1. Step 1: Analyze the query fields

   The query asks for book with id "1", requesting title and nested author name.

2. Step 2: Match query fields to response structure

   The response includes book object with title and author object containing name.

3. Final Answer:

   { "book": { "title": "1984", "author": { "name": "George Orwell" } } } -> Option A

4. Quick Check:

   Nested fields return nested objects [OK]

Hint: Nested fields return nested objects in response [OK]

Common Mistakes:

• Expecting flat objects for nested fields
• Missing nested author object
• Ignoring requested fields in response

4. This GraphQL query has an error:
query { user { name, email } }
Which is the most likely cause?

medium

A. The query is missing a closing brace.

B. GraphQL queries cannot have commas between fields.

C. Fields 'name' and 'email' cannot be requested together.

D. The server schema does not have a 'user' field.

Solution

1. Step 1: Check query syntax

   The query syntax is correct with braces and commas properly placed.

2. Step 2: Consider schema compatibility

   If the server schema lacks 'user' field, the query will fail despite correct syntax.

3. Final Answer:

   The server schema does not have a 'user' field. -> Option D

4. Quick Check:

   Schema mismatch causes query errors [OK]

Hint: Check if fields exist in server schema [OK]

Common Mistakes:

• Assuming syntax error when schema is missing fields
• Thinking commas are not allowed between fields
• Believing fields cannot be requested together

5. A client wants to fetch a list of products with only their names and prices to improve app speed. Which GraphQL feature helps achieve this?

hard

A. Requesting only specific fields in the query to reduce data transfer.

B. Using mutations to update product data.

C. Fetching all product details and filtering on the client side.

D. Using subscriptions to get real-time updates.

Solution

1. Step 1: Understand the client's goal

   The client wants to improve speed by reducing unnecessary data.

2. Step 2: Identify GraphQL feature that fits

   GraphQL allows requesting only needed fields, minimizing data sent over network.

3. Final Answer:

   Requesting only specific fields in the query to reduce data transfer. -> Option A

4. Quick Check:

   Selective field requests improve performance [OK]

Hint: Ask only for needed fields to speed up apps [OK]

Common Mistakes:

• Confusing queries with mutations
• Fetching all data then filtering client-side
• Using subscriptions when not needed