Why GraphQL performance needs attention - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to fetch user data with GraphQL.

GraphQL

query { user(id: [1]) { name email } }

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

A"123"

B123

CuserId

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using an unquoted number for the ID causes errors.

The user ID must be a string in quotes in GraphQL queries.

2fill in blank

medium

Complete the code to request posts with their titles and authors.

GraphQL

query { posts { title [1] { name } } }

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

Aauthor

Bwriter

CauthorName

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect field names causes no data to return.

The field to get the author of a post is usually called 'author'.

3fill in blank

hard

Fix the error in the query to avoid requesting too much data.

GraphQL

query { users { id name [1] } }

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

AallPosts { title }

Bposts { title content comments { text } }

Cposts

Dposts { title }

Attempts:

3 left

💡 Hint

Common Mistakes

Requesting full post content and comments causes slow queries.

Requesting only the post titles reduces data size and improves performance.

4fill in blank

hard

Fill both blanks to limit query results and improve performance.

GraphQL

query { posts(limit: [1]) { title author { name } [2] } }

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

A5

B10

Ccomments { text }

Dlikes

Attempts:

3 left

💡 Hint

Common Mistakes

Not limiting results or requesting too many nested fields slows queries.

Limiting posts to 5 and requesting only comments text helps keep queries fast.

5fill in blank

hard

Fill all three blanks to create an efficient query with filters.

GraphQL

query { posts(filter: { authorId: [1], published: [2] }) { title [3] } }

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

A"123"

Btrue

Ccomments { text }

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted IDs or requesting unnecessary fields causes slow queries.

Filtering posts by author ID and published status, and requesting comments text, keeps queries focused and efficient.

Practice

1. Why does GraphQL require special attention to performance compared to REST APIs?

easy

A. Because clients can request complex nested data in a single query

B. Because GraphQL only supports simple queries

C. Because GraphQL does not allow filtering data

D. Because GraphQL always caches all responses automatically

Solution

1. Step 1: Understand GraphQL query flexibility

   GraphQL lets clients request exactly the data they want, including deeply nested related data in one query.

2. Step 2: Recognize impact on performance

   This flexibility can cause complex queries that require more server processing and database work, slowing performance.

3. Final Answer:

   Because clients can request complex nested data in a single query -> Option A

4. Quick Check:

   Complex queries need attention = A [OK]

Hint: GraphQL queries can be complex and nested [OK]

Common Mistakes:

• Thinking GraphQL only supports simple queries
• Assuming GraphQL caches all responses automatically
• Believing GraphQL disallows filtering data

2. Which of the following is the correct way to limit the number of items returned in a GraphQL query?

easy

A. query { users(limit: 10) { id name } }

B. query { users(first: 10) { id name } }

C. query { users(max: 10) { id name } }

D. query { users(count: 10) { id name } }

Solution

1. Step 1: Recall GraphQL pagination arguments

   GraphQL commonly uses arguments like first or last to limit results, not limit, max, or count.

2. Step 2: Identify correct syntax

   The correct syntax to limit to 10 items is first: 10.

3. Final Answer:

   query { users(first: 10) { id name } } -> Option B

4. Quick Check:

   Use 'first' to limit items = D [OK]

Hint: Use 'first' argument to limit items in GraphQL [OK]

Common Mistakes:

• Using SQL-like 'limit' instead of 'first'
• Using unsupported arguments like 'max' or 'count'
• Confusing argument names for pagination

3. Given this GraphQL query:

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

What is the main performance concern with this query?

medium

A. It uses an invalid syntax for the user ID

B. It does not specify any fields to return

C. It requests deeply nested related data which may cause slow database joins

D. It limits the number of posts to 1

Solution

1. Step 1: Analyze query structure

   The query requests a user, their posts, and comments on those posts, which is deeply nested.

2. Step 2: Understand performance impact

   Fetching nested data can cause multiple database joins or queries, increasing response time and server load.

3. Final Answer:

   It requests deeply nested related data which may cause slow database joins -> Option C

4. Quick Check:

   Deep nesting slows queries = B [OK]

Hint: Deep nesting in queries can slow performance [OK]

Common Mistakes:

• Thinking the ID syntax is invalid
• Believing no fields are selected
• Assuming the query limits posts

4. You have a GraphQL query that fetches a list of products with their categories and reviews. The query is slow. Which change will most likely improve performance?

medium

A. Request all products without any limits

B. Add more nested fields to the reviews

C. Use a query without any filters

D. Remove the reviews field from the query

Solution

1. Step 1: Identify heavy parts of the query

   Reviews often have many entries and nested data, which can slow down the query.

2. Step 2: Simplify the query

   Removing the reviews field reduces data fetched and processing, improving performance.

3. Final Answer:

   Remove the reviews field from the query -> Option D

4. Quick Check:

   Removing heavy nested fields speeds queries = C [OK]

Hint: Remove heavy nested fields to speed queries [OK]

Common Mistakes:

• Adding more nested fields worsens performance
• Requesting all products without limits slows queries
• Using no filters fetches too much data

5. A client sends this GraphQL query:

query { orders { id total customer { id name orders { id } } } }

Why might this query cause performance problems, and how can you fix it?

hard

A. It causes a recursive data fetch; fix by limiting nested orders inside customer

B. It uses invalid field names; fix by correcting field names

C. It fetches too few fields; fix by adding more fields

D. It uses deprecated syntax; fix by updating to new syntax

Solution

1. Step 1: Identify recursive nesting

   The query fetches orders, then for each order's customer, fetches their orders again, causing potential infinite recursion or very large data.

2. Step 2: Apply query limits

   Limiting or removing nested orders inside customer breaks recursion and reduces data size, improving performance.

3. Final Answer:

   It causes a recursive data fetch; fix by limiting nested orders inside customer -> Option A

4. Quick Check:

   Recursive nesting hurts performance = A [OK]

Hint: Avoid recursive nested queries; limit nested data [OK]

Common Mistakes:

• Thinking field names are invalid
• Assuming more fields improve performance
• Believing syntax is deprecated