GraphQL vs REST comparison - Quick Revision & Key Differences

Recall & Review

beginner

What is the main difference between GraphQL and REST in how they fetch data?

GraphQL allows clients to request exactly the data they need in a single query, while REST typically requires multiple endpoints and requests to fetch related data.

intermediate

How does GraphQL handle versioning compared to REST?

GraphQL avoids versioning by evolving the schema and allowing clients to request only the fields they want, whereas REST often uses versioned endpoints to manage changes.

intermediate

What is a key advantage of REST's use of HTTP methods over GraphQL?

REST uses standard HTTP methods (GET, POST, PUT, DELETE) which are well understood and supported by tools and infrastructure, making it simple to cache and secure.

beginner

Why might GraphQL reduce over-fetching and under-fetching of data?

Because clients specify exactly which fields they want in a query, GraphQL avoids sending too much or too little data compared to REST endpoints that return fixed data structures.

advanced

What is a common challenge when using GraphQL compared to REST?

GraphQL can be more complex to set up and optimize, especially for caching and error handling, while REST benefits from simpler, well-known patterns.

Which of the following best describes how GraphQL queries work?

A Clients receive all data from the server regardless of need

B Clients must call multiple endpoints to get related data

C Clients use HTTP methods to fetch data

D Clients specify exactly what data they want in a single request

GraphQL lets clients request exactly the data they want in one query.

How does REST typically handle API versioning?

A By using versioned endpoints like /v1/, /v2/

B By evolving the schema without versions

C By letting clients choose fields dynamically

D By using GraphQL queries

REST often uses versioned URLs to manage changes in the API.

What is a benefit of REST's use of HTTP methods?

A They allow clients to specify fields dynamically

B They simplify caching and security with standard methods

C They reduce the number of requests needed

D They eliminate the need for endpoints

Standard HTTP methods help with caching and security in REST.

Why might GraphQL reduce over-fetching of data?

A Because clients specify exactly which fields they want

B Because it caches all responses

C Because it uses multiple endpoints

D Because it returns all data by default

GraphQL queries specify exactly the needed fields, avoiding extra data.

What is a common challenge when adopting GraphQL?

A It has no support for querying data

B It is simpler than REST to implement

C It can be complex to optimize caching and error handling

D It requires multiple endpoints for each resource

GraphQL can be complex to set up caching and error handling compared to REST.

Explain the main differences between GraphQL and REST in how they handle data fetching and versioning.

Think about how clients ask for data and how APIs change over time.

Describe one advantage and one challenge of using GraphQL compared to REST.

Consider what makes GraphQL flexible but also what makes it harder to manage.

Practice

1. What is a key advantage of GraphQL compared to REST when fetching data?

easy

A. GraphQL does not support querying nested data.

B. GraphQL requires multiple URLs for different data resources.

C. GraphQL uses fixed data shapes for each resource.

D. GraphQL allows fetching exactly the data you want in a single request.

Solution

1. Step 1: Understand GraphQL data fetching

   GraphQL lets clients specify exactly what data they want in one request, avoiding over-fetching or under-fetching.

2. Step 2: Compare with REST approach

   REST typically requires multiple URLs and fixed data shapes, which can lead to multiple requests or extra data.

3. Final Answer:

   GraphQL allows fetching exactly the data you want in a single request. -> Option D

4. Quick Check:

   GraphQL = precise single-request data fetching [OK]

Hint: GraphQL = one request, exact data [OK]

Common Mistakes:

• Thinking GraphQL needs multiple URLs
• Believing GraphQL returns fixed data shapes
• Assuming GraphQL can't query nested data

2. Which of the following is the correct way to define a GraphQL query to get a user's name and email?

easy

A. { user: { name, email } }

B. query { user { name, email } }

C. SELECT name, email FROM user

D. GET /user/name,email

Solution

1. Step 1: Identify GraphQL query syntax

   GraphQL queries start with the keyword 'query' followed by the requested fields inside braces.

2. Step 2: Check each option

   query { user { name, email } } matches GraphQL syntax. GET /user/name,email is REST style URL. SELECT name, email FROM user is SQL. { user: { name, email } } is invalid JSON-like structure.

3. Final Answer:

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

4. Quick Check:

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

Hint: GraphQL queries start with 'query' keyword [OK]

Common Mistakes:

• Using REST or SQL syntax instead of GraphQL
• Omitting the 'query' keyword
• Incorrect braces placement

3. Given this GraphQL query:

query { book(id: "1") { title author { name } } }

What data structure will the response most likely contain?

medium

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

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

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

D. {"data": {"book": {"title": "1984", "author": ["George Orwell"]}}}

Solution

1. Step 1: Understand GraphQL response format

   GraphQL responses wrap data inside a 'data' object, matching the query structure exactly.

2. Step 2: Match nested fields

   The query requests 'book' with 'title' and nested 'author' with 'name', so response must reflect nested objects.

3. Final Answer:

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

4. Quick Check:

   GraphQL response = nested 'data' object [OK]

Hint: GraphQL responses wrap data inside 'data' key [OK]

Common Mistakes:

• Omitting the 'data' wrapper
• Flattening nested objects incorrectly
• Using arrays for single nested objects

4. Identify the error in this GraphQL query:

query { user(id: 5) { name, email } }

medium

A. The query keyword is missing.

B. The fields 'name' and 'email' should be inside parentheses.

C. The id value should be a string, so it needs quotes.

D. GraphQL does not support querying users by id.

Solution

1. Step 1: Check argument types in GraphQL

   GraphQL requires string arguments to be quoted. Here, id is likely a string and should be "5".

2. Step 2: Verify field syntax

   Fields 'name' and 'email' are correctly listed with commas, no parentheses needed.

3. Final Answer:

   The id value should be a string, so it needs quotes. -> Option C

4. Quick Check:

   String arguments need quotes in GraphQL [OK]

Hint: Quote string arguments in GraphQL queries [OK]

Common Mistakes:

• Leaving string arguments unquoted
• Adding parentheses around fields
• Assuming query keyword is optional

5. You want to design an API for a mobile app that needs flexible data fetching with minimal requests and efficient caching. Which approach is best and why?

hard

A. Use GraphQL because it allows clients to request exactly what they need in one request.

B. Use REST because it is simpler and caches well with fixed URLs.

C. Use REST because it supports nested queries better than GraphQL.

D. Use GraphQL because it requires multiple requests for different data.

Solution

1. Step 1: Analyze requirements for flexible data fetching and minimal requests

   GraphQL excels at letting clients specify exactly what data they want, reducing multiple requests.

2. Step 2: Consider caching and efficiency

   While REST is simpler and caches well, GraphQL's single-request flexibility suits mobile apps needing efficient data transfer.

3. Final Answer:

   Use GraphQL because it allows clients to request exactly what they need in one request. -> Option A

4. Quick Check:

   Flexible, minimal requests = GraphQL [OK]

Hint: Flexible single-request fetching = GraphQL [OK]

Common Mistakes:

• Choosing REST for flexibility over GraphQL
• Thinking GraphQL needs multiple requests
• Assuming REST handles nested queries better