Why mutations modify data in GraphQL - Performance Analysis

Time Complexity: Why mutations modify data

O(n)

Understanding Time Complexity

When we use mutations in GraphQL, we change data on the server. It is important to understand how the time it takes to do this changes as the data grows.

We want to know: How does the work grow when we modify more or bigger data?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

mutation UpdateUserName($id: ID!, $newName: String!) {
  updateUser(id: $id, name: $newName) {
    id
    name
  }
}
    

This mutation updates the name of one user by their ID and returns the updated user data.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Finding the user by ID and updating their name.
• How many times: This happens once per mutation call, affecting one user.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10 users	About 10 steps to find and update one user
100 users	About 100 steps to find and update one user
1000 users	About 1000 steps to find and update one user

Pattern observation: The time to find and update grows roughly in direct proportion to the number of users.

Final Time Complexity

Time Complexity: O(n)

This means the time to update one user grows linearly with the number of users in the system.

Common Mistake

[X] Wrong: "Updating one user always takes the same time, no matter how many users exist."

[OK] Correct: If the system searches users one by one, more users mean more searching time before updating.

Interview Connect

Understanding how mutations scale helps you explain how your app handles data changes efficiently. This skill shows you think about real-world data growth and performance.

Self-Check

"What if the users were stored in a way that lets us find one instantly? How would the time complexity change?"

Practice

1. What is the main purpose of a mutation in GraphQL?

easy

A. To modify data by adding, updating, or deleting it

B. To only fetch data without changes

C. To define the schema structure

D. To create a new query type

Solution

1. Step 1: Understand the role of mutations

   Mutations are designed to change data, unlike queries which only fetch data.

2. Step 2: Identify the correct purpose

   Since mutations add, update, or delete data, their main purpose is to modify data.

3. Final Answer:

   To modify data by adding, updating, or deleting it -> Option A

4. Quick Check:

   Mutation = Modify data [OK]

Hint: Mutations always change data, queries only read data [OK]

Common Mistakes:

• Confusing mutations with queries
• Thinking mutations only fetch data
• Believing mutations define schema only

2. Which of the following is the correct way to start a mutation operation in GraphQL?

easy

A. modify { updateUser(id: 1) { name } }

B. query { updateUser(id: 1) { name } }

C. update { updateUser(id: 1) { name } }

D. mutation { updateUser(id: 1) { name } }

Solution

1. Step 1: Identify the keyword for mutations

   GraphQL uses the keyword mutation to start mutation operations.

2. Step 2: Check the options

   Only mutation { updateUser(id: 1) { name } } uses the correct mutation keyword to start the operation.

3. Final Answer:

   mutation { updateUser(id: 1) { name } } -> Option D

4. Quick Check:

   Mutation keyword = mutation [OK]

Hint: Mutations always start with the 'mutation' keyword [OK]

Common Mistakes:

• Using 'query' instead of 'mutation'
• Using non-existent keywords like 'update' or 'modify'
• Omitting the mutation keyword

3. Given the mutation below, what will be the result if the user with id 2 exists?

mutation {
  updateUser(id: 2, input: {name: "Alice"}) {
    id
    name
  }
}

medium

A. Syntax error due to missing input type

B. { "data": { "updateUser": null } }

C. { "data": { "updateUser": { "id": 2, "name": "Alice" } } }

D. No change, returns old user data

Solution

1. Step 1: Understand mutation behavior

   The mutation updates user with id 2, changing the name to "Alice".

2. Step 2: Predict the returned data

   The mutation returns the updated user data with id and new name.

3. Final Answer:

   { "data": { "updateUser": { "id": 2, "name": "Alice" } } } -> Option C

4. Quick Check:

   Mutation updates and returns new data [OK]

Hint: Mutations return updated data if successful [OK]

Common Mistakes:

• Assuming mutation returns null on success
• Thinking mutation causes syntax error here
• Believing mutation returns old data without changes

4. Identify the error in this mutation:

mutation {
  addUser(name: "Bob")
  {
    id
    name
  }
}

medium

A. Mutation keyword is incorrect

B. Missing input argument object for addUser

C. Curly braces are misplaced

D. No error, mutation is correct

Solution

1. Step 1: Check mutation input format

   Mutations usually require input as an object, e.g., addUser(input: {name: "Bob"}).

2. Step 2: Identify missing input argument

   The mutation lacks the input argument object, causing an error.

3. Final Answer:

   Missing input argument object for addUser -> Option B

4. Quick Check:

   Input argument missing = error [OK]

Hint: Mutations need input objects for data changes [OK]

Common Mistakes:

• Forgetting to wrap inputs in an object
• Misplacing curly braces
• Confusing mutation keyword

5. You want to delete a user and then immediately fetch the updated user list in one mutation operation. Which approach correctly uses mutations to achieve this?

hard

A. Use a single mutation with two fields: deleteUser and users to delete and fetch updated list

B. Use a query to delete the user and a mutation to fetch the list

C. Use two separate mutations, one for deleting and one for fetching users

D. Use a mutation to delete the user and a query to fetch the updated list separately

Solution

1. Step 1: Understand mutation capabilities

   GraphQL mutations can include multiple fields to perform several operations in one request.

2. Step 2: Identify correct approach

   Using a single mutation with deleteUser and users fields allows deleting and fetching updated data atomically.

3. Final Answer:

   Use a single mutation with two fields: deleteUser and users to delete and fetch updated list -> Option A

4. Quick Check:

   Single mutation can do multiple related operations [OK]

Hint: Combine delete and fetch in one mutation for atomic update [OK]

Common Mistakes:

• Trying to delete with a query
• Splitting operations into separate requests unnecessarily
• Using mutation only for delete without fetching updated data