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?