Query complexity analysis in GraphQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is query complexity analysis in GraphQL?

It is a method to measure how 'heavy' or 'costly' a GraphQL query is, helping to prevent very expensive queries that can slow down or crash a server.

beginner

Why do we need to analyze query complexity in GraphQL?

Because GraphQL allows clients to ask for exactly what they want, some queries can be very large or nested deeply, which can overload the server. Complexity analysis helps keep the server safe and fast.

intermediate

How is query complexity usually calculated?

By assigning a cost to each field and summing these costs, including nested fields, to get a total score representing the query's complexity.

beginner

What happens if a GraphQL query exceeds the allowed complexity limit?

The server rejects the query and returns an error, preventing the execution of very expensive queries.

intermediate

Name one common technique to reduce query complexity in GraphQL.

Limiting the depth of nested queries or restricting the number of items returned in lists are common ways to reduce complexity.

What does query complexity analysis help prevent in GraphQL?

A Server overload from expensive queries

B Syntax errors in queries

C Unauthorized access to data

D Slow network connections

Query complexity analysis helps prevent server overload by rejecting very expensive queries.

How is the complexity of a GraphQL query typically measured?

A By checking the query's execution time after running

B By counting the number of characters in the query

C By assigning costs to fields and summing them

D By the number of users running the query

Complexity is measured by assigning costs to each field and summing them, including nested fields.

What is a common response when a query exceeds the complexity limit?

A The server runs the query anyway

B The server caches the query for later

C The server slows down gradually

D The server returns an error and rejects the query

The server rejects queries that exceed the complexity limit to protect resources.

Which of these can help reduce query complexity?

A Increasing the number of nested fields

B Limiting the depth of nested queries

C Requesting all available fields

D Using very large lists

Limiting nested query depth reduces complexity and server load.

Why is query complexity analysis especially important in GraphQL?

A Because clients can request deeply nested and large data sets

B Because GraphQL queries are always simple

C Because GraphQL does not support nested queries

D Because GraphQL queries are always cached

GraphQL allows clients to request exactly what they want, including deeply nested data, which can be costly.

Explain what query complexity analysis is and why it matters in GraphQL.

Think about how some queries can be very large or nested.

Describe how query complexity is calculated and what happens if a query is too complex.

Consider how the server decides if a query is allowed.

Practice

1. What is the main purpose of query complexity analysis in GraphQL?

easy

A. To measure how resource-heavy a query is before execution

B. To change the data returned by a query

C. To write queries faster

D. To store query results in cache

Solution

1. Step 1: Understand query complexity analysis

   It estimates how much work a query will cause the server to do before running it.

2. Step 2: Identify the main goal

   This helps prevent very heavy queries that slow down or crash the server.

3. Final Answer:

   To measure how resource-heavy a query is before execution -> Option A

4. Quick Check:

   Query complexity = resource estimation [OK]

Hint: Think: Why check query cost before running? To protect server [OK]

Common Mistakes:

• Confusing complexity analysis with caching
• Thinking it changes query results
• Assuming it speeds up query writing

2. Which of the following is a correct way to define a complexity rule in a GraphQL server?

easy

A. Adding a complexity function to field definitions

B. Writing complexity inside the GraphQL query itself

C. Using @complexity directive in the query

D. Setting complexity in the client application

Solution

1. Step 1: Recall where complexity rules are set

   Complexity rules are added in the server schema code, usually as functions on fields.

2. Step 2: Eliminate wrong options

   Complexity is not set inside queries, directives, or client apps.

3. Final Answer:

   Adding a complexity function to field definitions -> Option A

4. Quick Check:

   Complexity rules = server schema code [OK]

Hint: Complexity rules live on server fields, not in queries [OK]

Common Mistakes:

• Trying to add complexity in the query text
• Using non-existent directives for complexity
• Setting complexity on client side

3. Given this GraphQL query and complexity rules:

{ user { posts { comments } } }

If user has complexity 1, posts complexity 5, and comments complexity 2, what is the total complexity?

medium

A. 8

B. 15

C. 7

D. 10

Solution

1. Step 1: Identify field complexities

   user = 1, posts = 5, comments = 2.

2. Step 2: Calculate for nested fields

   Nested field complexities are multiplied: 1 x 5 x 2 = 10.

3. Final Answer:

   10 -> Option D

4. Quick Check:

   Nested fields multiply complexity = 1*5*2=10 [OK]

Hint: Multiply all nested field complexities: 1 x 5 x 2 = 10 [OK]

Common Mistakes:

• Adding all numbers without multiplication
• Ignoring nested field multiplication
• Choosing sum instead of product for nested fields

4. You wrote a complexity function for a field but your server crashes on some queries. What is a likely cause?

medium

A. The query is missing required fields

B. You forgot to add the field to the schema

C. The complexity function returns a non-numeric value

D. The client sent an invalid query syntax

Solution

1. Step 1: Understand complexity function requirements

   Complexity functions must return numbers representing cost.

2. Step 2: Identify crash cause

   If the function returns a string or undefined, the server cannot calculate total complexity and crashes.

3. Final Answer:

   The complexity function returns a non-numeric value -> Option C

4. Quick Check:

   Complexity function must return number [OK]

Hint: Ensure complexity functions return numbers only [OK]

Common Mistakes:

• Returning strings or null from complexity functions
• Ignoring schema registration of fields
• Blaming client query syntax for server crashes

5. You want to limit your GraphQL server to reject queries with complexity over 100. Which approach correctly implements this?

hard

A. Modify client queries to never exceed 100 complexity

B. Add a complexity rule that calculates total cost and rejects queries above 100

C. Use a directive in queries to mark complexity limits

D. Increase server timeout to handle heavy queries

Solution

1. Step 1: Understand server-side complexity limiting

   The server must calculate query complexity and reject queries exceeding the limit.

2. Step 2: Evaluate options

   Only adding a complexity rule on the server can enforce this limit automatically.

3. Final Answer:

   Add a complexity rule that calculates total cost and rejects queries above 100 -> Option B

4. Quick Check:

   Server enforces limits via complexity rules [OK]

Hint: Limit complexity on server, not client or query text [OK]

Common Mistakes:

• Trying to limit complexity from client side
• Using query directives which don't enforce limits
• Increasing timeout instead of limiting complexity