Transaction handling in GraphQL - Time & Space Complexity

Time Complexity: Transaction handling

O(n)

Understanding Time Complexity

When working with transactions in databases, it's important to know how the time to complete them changes as more operations are included.

We want to understand how the number of steps grows when handling multiple actions inside a transaction.

Scenario Under Consideration

Analyze the time complexity of the following GraphQL transaction handling snippet.

mutation PerformTransaction($actions: [ActionInput!]!) {
  startTransaction {
    id
  }
  performActions(actions: $actions) {
    success
  }
  commitTransaction {
    status
  }
}

This code starts a transaction, performs a list of actions, then commits the transaction.

Identify Repeating Operations

Look for repeated steps inside the transaction.

• Primary operation: Performing each action in the actions list.
• How many times: Once for each action in the input list.

How Execution Grows With Input

As the number of actions increases, the time to perform them grows proportionally.

Input Size (n)	Approx. Operations
10	About 10 action executions
100	About 100 action executions
1000	About 1000 action executions

Pattern observation: The total work grows directly with the number of actions.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the transaction grows linearly with the number of actions inside it.

Common Mistake

[X] Wrong: "Starting and committing a transaction takes as much time as performing all actions inside it."

[OK] Correct: Starting and committing are usually fixed steps and take about the same time regardless of actions, so the main time depends on how many actions are performed.

Interview Connect

Understanding how transaction time grows helps you design efficient database operations and shows you can reason about performance in real projects.

Self-Check

"What if we batch multiple actions together inside a single performActions call? How would that affect the time complexity?"