Why resolvers connect schema to data in GraphQL - Performance Analysis

Time Complexity: Why resolvers connect schema to data

O(n)

Understanding Time Complexity

When using GraphQL, resolvers are the parts that fetch data for each field in the schema.

We want to understand how the time to get data grows as the amount of data or requests grows.

Scenario Under Consideration

Analyze the time complexity of the following resolver code snippet.

    type Query {
      books: [Book]
    }

    type Book {
      title: String
      author: Author
    }

    type Author {
      name: String
    }

    const resolvers = {
      Query: {
        books: () => fetchAllBooks()
      },
      Book: {
        author: (book) => fetchAuthorById(book.authorId)
      }
    }
    

This code fetches a list of books, then for each book fetches its author data.

Identify Repeating Operations

Look for repeated data fetching steps.

• Primary operation: Fetching authors for each book.
• How many times: Once for each book in the list.

How Execution Grows With Input

As the number of books grows, the number of author fetches grows too.

Input Size (n books)	Approx. Operations
10	10 author fetches + 1 books fetch
100	100 author fetches + 1 books fetch
1000	1000 author fetches + 1 books fetch

Pattern observation: The number of author fetches grows directly with the number of books.

Final Time Complexity

Time Complexity: O(n)

This means the time to get all data grows in a straight line as the number of books increases.

Common Mistake

[X] Wrong: "Fetching authors for each book happens all at once and does not add extra time."

[OK] Correct: Each author fetch is a separate operation, so more books mean more fetches and more time.

Interview Connect

Understanding how resolvers fetch data step-by-step helps you explain how your code handles growing data smoothly.

Self-Check

What if the author data was included inside each book record already? How would the time complexity change?

Practice

1. What is the main role of a resolver in GraphQL?

easy

A. To fetch or compute the data for a specific field in the schema

B. To define the structure of the GraphQL schema

C. To handle user authentication and authorization

D. To format the query string before execution

Solution

1. Step 1: Understand the purpose of resolvers

   Resolvers are functions that run when a field in the schema is requested to provide the actual data.

2. Step 2: Differentiate from schema definition

   The schema defines the shape of data, but resolvers connect those fields to real data sources or computations.

3. Final Answer:

   To fetch or compute the data for a specific field in the schema -> Option A

4. Quick Check:

   Resolvers fetch data = A [OK]

Hint: Resolvers provide data for fields, not schema or auth [OK]

Common Mistakes:

• Confusing resolvers with schema definitions
• Thinking resolvers handle authentication
• Believing resolvers format queries

2. Which of the following is the correct syntax for a simple resolver function in GraphQL?

easy

A. const resolver = (parent; args; context) => data;

B. const resolver = { parent, args, context } => data;

C. const resolver = (parent, args, context) => data;

D. const resolver = (parent args context) => data;

Solution

1. Step 1: Recall JavaScript arrow function syntax

   Arrow functions use parentheses for parameters separated by commas, e.g., (a, b, c) => result.

2. Step 2: Check each option's parameter syntax

   const resolver = (parent, args, context) => data; uses commas correctly; A uses semicolons instead of commas; B uses braces instead of parentheses; D misses commas.

3. Final Answer:

   const resolver = (parent, args, context) => data; -> Option C

4. Quick Check:

   Arrow function params need commas = C [OK]

Hint: Arrow function params need commas inside parentheses [OK]

Common Mistakes:

• Using braces {} instead of parentheses () for parameters
• Separating parameters with semicolons
• Omitting commas between parameters

3. Given this resolver snippet, what will be the output when querying userName?

const resolvers = {
  Query: {
    userName: () => "Alice"
  }
};

medium

A. "Alice"

B. "userName"

C. null

D. Error: resolver not found

Solution

1. Step 1: Identify the resolver function for userName

   The resolver for userName returns the string "Alice" directly.

2. Step 2: Understand the query result

   When the userName field is queried, the resolver returns "Alice", so the output is "Alice".

3. Final Answer:

   "Alice" -> Option A

4. Quick Check:

   Resolver returns "Alice" = B [OK]

Hint: Resolver return value is the query output [OK]

Common Mistakes:

• Confusing field name with returned value
• Expecting null if no arguments
• Assuming error without resolver

4. Identify the error in this resolver code snippet:

const resolvers = {
  Query: {
    userAge: (parent, args) => {
      return args.age
    }
  }
};

// Query: { userAge }
// Variables: {}

medium

A. Missing context parameter in resolver

B. Resolver expects argument 'age' but none provided in query

C. Resolver should return parent instead of args.age

D. Syntax error: missing semicolon after return

Solution

1. Step 1: Check resolver parameters and usage

   The resolver expects an argument named 'age' from args to return.

2. Step 2: Analyze the query and variables

   The query requests userAge but provides no variables, so args.age is undefined.

3. Final Answer:

   Resolver expects argument 'age' but none provided in query -> Option B

4. Quick Check:

   Missing argument in query = D [OK]

Hint: Check if query provides needed args for resolver [OK]

Common Mistakes:

• Assuming context is always required
• Ignoring missing query variables
• Thinking missing semicolon causes error here

5. You want to fetch a user's full profile by combining data from two sources: a database and an external API. How should you design the resolver for the userProfile field?

hard

A. Fetch data only from the database and ignore the API

B. Define the schema to include both data sources without a resolver

C. Use two separate resolvers for the same field to fetch data independently

D. Write a resolver that calls the database and API, then merges results before returning

Solution

1. Step 1: Understand resolver role in combining data

   Resolvers can run code to fetch and combine data from multiple sources before returning.

2. Step 2: Evaluate options for fetching and merging data

   Write a resolver that calls the database and API, then merges results before returning correctly describes writing a resolver that calls both sources and merges results. Other options either ignore data sources or misuse resolvers.

3. Final Answer:

   Write a resolver that calls the database and API, then merges results before returning -> Option D

4. Quick Check:

   Resolvers combine data sources = A [OK]

Hint: Combine data in one resolver function for the field [OK]

Common Mistakes:

• Expecting schema alone to fetch data
• Trying multiple resolvers for one field
• Ignoring one data source