Why relationships model real data in GraphQL - Performance Analysis

Time Complexity: Why relationships model real data

O(n * m)

Understanding Time Complexity

When we use relationships in data, we connect pieces of information together. Understanding how this connection affects the work done by a query helps us see how fast or slow it runs as data grows.

We want to know: How does the time to get related data change when we have more items?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

query GetAuthorsAndBooks {
  authors {
    id
    name
    books {
      id
      title
    }
  }
}
    

This query fetches a list of authors and, for each author, fetches their books. It shows how relationships connect authors to their books.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: For each author, fetching their list of books.
• How many times: The books fetching repeats once per author.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n authors)	Approx. Operations (authors + their books)
10	Fetching 10 authors and their books (say 3 books each) = about 40 operations
100	Fetching 100 authors and their books (3 books each) = about 400 operations
1000	Fetching 1000 authors and their books (3 books each) = about 4000 operations

Pattern observation: As the number of authors grows, the total work grows roughly in proportion to authors times their books.

Final Time Complexity

Time Complexity: O(n * m)

This means the time grows with the number of authors (n) times the average number of books per author (m). More authors or more books per author means more work.

Common Mistake

[X] Wrong: "Fetching related data is always just as fast as fetching the main data."

[OK] Correct: Because each related list (like books per author) adds extra work. The more related items, the more time it takes.

Interview Connect

Understanding how relationships affect query time helps you explain real data fetching scenarios clearly. It shows you can think about how data size impacts performance, a useful skill in many jobs.

Self-Check

"What if each author had a fixed number of books, but we added a new level of related data like reviews for each book? How would the time complexity change?"