GraphQL vs REST comparison - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a GraphQL query that fetches a user's name.

GraphQL

query { user(id: "1") { [1] } }

Drag options to blanks, or click blank then click option'

Apassword

Bname

Cemail

Daddress

Attempts:

3 left

💡 Hint

Common Mistakes

Using fields like email or password instead of name.

The field name is used to fetch the user's name in GraphQL queries.

2fill in blank

medium

Complete the code to specify the HTTP method used by REST to retrieve data.

GraphQL

fetch('/api/users', { method: '[1]' })

Drag options to blanks, or click blank then click option'

AGET

BDELETE

CPUT

DPOST

Attempts:

3 left

💡 Hint

Common Mistakes

Using POST or PUT instead of GET for data retrieval.

REST uses the GET method to retrieve data from the server.

3fill in blank

hard

Fix the error in the GraphQL query to fetch a user's email.

GraphQL

query { user(id: "1") { [1] } }

Drag options to blanks, or click blank then click option'

Aemail

Bmail

CuserEmail

Demails

Attempts:

3 left

💡 Hint

Common Mistakes

Using plural or incorrect field names like emails or mail.

The correct field to fetch a user's email in GraphQL is email.

4fill in blank

hard

Fill both blanks to complete the REST API call that updates a user's name.

GraphQL

fetch('/api/users/1', { method: '[1]', body: JSON.stringify({ name: '[2]' }) })

Drag options to blanks, or click blank then click option'

APUT

BJohn

CGET

DDELETE

Attempts:

3 left

💡 Hint

Common Mistakes

Using GET or DELETE instead of PUT for updates.

REST uses PUT to update data, and the new name is John.

5fill in blank

hard

Fill all three blanks to complete a GraphQL mutation that updates a user's email.

GraphQL

mutation { updateUser(id: "1", input: { [1]: "[2]" }) { [3] } }

Drag options to blanks, or click blank then click option'

Aemail

[e-mail]

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong field names or returning the wrong field.

The mutation updates the email field with the new email and returns the updated email.

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