Return values on write in DynamoDB - Time & Space Complexity

Time Complexity: Return values on write

O(n)

Understanding Time Complexity

When we write data to DynamoDB and ask it to return values, the time it takes can change depending on what we ask back.

We want to understand how the cost grows when we ask DynamoDB to return different amounts of data after a write.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    const params = {
      TableName: "Users",
      Key: { "UserId": "123" },
      UpdateExpression: "set Age = :age",
      ExpressionAttributeValues: { ":age": 30 },
      ReturnValues: "ALL_NEW"
    };
    
    dynamodb.update(params, (err, data) => {
      if (err) console.log(err);
      else console.log(data.Attributes);
    });
    

This code updates a user's age and asks DynamoDB to return all the new attributes after the update.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: DynamoDB reads the updated item attributes to return them.
• How many times: This happens once per write request.

How Execution Grows With Input

When you ask DynamoDB to return more attributes after a write, it reads more data to send back.

Input Size (attributes returned)	Approx. Operations
10	Reads 10 attributes
100	Reads 100 attributes
1000	Reads 1000 attributes

Pattern observation: The work grows roughly in direct proportion to how many attributes you ask to be returned.

Final Time Complexity

Time Complexity: O(n)

This means the time to return values after a write grows linearly with the number of attributes returned.

Common Mistake

[X] Wrong: "Returning values after a write always takes the same time no matter how much data is returned."

[OK] Correct: Returning more attributes means DynamoDB reads and sends more data, so it takes more time.

Interview Connect

Understanding how return values affect write time helps you explain trade-offs clearly and shows you know how database operations scale.

Self-Check

"What if we changed ReturnValues from ALL_NEW to NONE? How would the time complexity change?"

Practice

1. What does the ReturnValues parameter do in a DynamoDB write operation?

easy

A. It specifies what data should be returned after the write operation.

B. It controls the write capacity units consumed by the operation.

C. It sets the timeout duration for the write request.

D. It defines the table where data will be written.

Solution

1. Step 1: Understand the role of ReturnValues

   The ReturnValues parameter tells DynamoDB what data to send back after a write, such as old or new item attributes.

2. Step 2: Differentiate from other parameters

   ReturnValues does not affect capacity, timeout, or table selection; it only controls returned data.

3. Final Answer:

   It specifies what data should be returned after the write operation. -> Option A

4. Quick Check:

   ReturnValues controls returned data [OK]

Hint: ReturnValues returns data after write, not capacity or timeout [OK]

Common Mistakes:

• Confusing ReturnValues with capacity settings
• Thinking it sets request timeout
• Assuming it selects the table

2. Which of the following is the correct syntax to request the old item attributes after an update in DynamoDB using ReturnValues?

easy

A. "UPDATED_NEW"

B. "NONE"

C. "ALL_NEW"

D. "ALL_OLD"

Solution

1. Step 1: Recall ReturnValues options

   ReturnValues can be NONE, ALL_OLD, UPDATED_OLD, ALL_NEW, UPDATED_NEW.

2. Step 2: Identify option for old attributes after update

   "ALL_OLD" returns the entire item as it was before the update.

3. Final Answer:

   "ALL_OLD" -> Option D

4. Quick Check:

   Old attributes = ALL_OLD [OK]

Hint: Old data after update is ALL_OLD [OK]

Common Mistakes:

• Using ALL_NEW to get old data
• Confusing UPDATED_NEW with old data
• Setting NONE expecting data back

3. Given this DynamoDB update command snippet:

{
  TableName: "Users",
  Key: { "UserId": "123" },
  UpdateExpression: "SET Age = :newAge",
  ExpressionAttributeValues: { ":newAge": 30 },
  ReturnValues: "UPDATED_NEW"
}

What will the response contain?

medium

A. The entire item before the update.

B. Only the new Age attribute after the update.

C. No attributes, just success confirmation.

D. The entire item after the update.

Solution

1. Step 1: Understand ReturnValues "UPDATED_NEW" meaning

   This option returns only the attributes that were updated with their new values.

2. Step 2: Apply to given update

   The update changes Age to 30, so response includes only Age with value 30.

3. Final Answer:

   Only the new Age attribute after the update. -> Option B

4. Quick Check:

   UPDATED_NEW returns updated attributes [OK]

Hint: UPDATED_NEW returns only changed attributes with new values [OK]

Common Mistakes:

• Expecting full item back with UPDATED_NEW
• Confusing UPDATED_NEW with ALL_NEW
• Assuming no data returned with UPDATED_NEW

4. You wrote this DynamoDB PutItem request:

{
  TableName: "Products",
  Item: { "Id": "001", "Name": "Pen" },
  ReturnValues: "UPDATED_OLD"
}

But you get an error. What is wrong?

medium

A. ReturnValues must be set to "ALL_NEW" for PutItem.

B. The Item attribute is missing required keys.

C. "UPDATED_OLD" is invalid for PutItem operations.

D. TableName is incorrect.

Solution

1. Step 1: Check ReturnValues compatibility with PutItem

   PutItem supports only NONE or ALL_OLD for ReturnValues; UPDATED_OLD is invalid.

2. Step 2: Confirm other parameters

   Item and TableName are correct; error is due to invalid ReturnValues.

3. Final Answer:

   "UPDATED_OLD" is invalid for PutItem operations. -> Option C

4. Quick Check:

   PutItem supports NONE or ALL_OLD only [OK]

Hint: PutItem allows NONE or ALL_OLD only for ReturnValues [OK]

Common Mistakes:

• Using UPDATED_OLD with PutItem
• Assuming ALL_NEW required for PutItem
• Mistaking missing keys as cause

5. You want to update a user's email in DynamoDB and get back the entire updated item in one request. Which ReturnValues option should you use in your UpdateItem call?

hard

A. "ALL_NEW"

B. "UPDATED_OLD"

C. "NONE"

D. "ALL_OLD"

Solution

1. Step 1: Understand the goal

   You want the full updated item returned after the update.

2. Step 2: Match ReturnValues option

   "ALL_NEW" returns the entire item as it looks after the update.

3. Final Answer:

   "ALL_NEW" -> Option A

4. Quick Check:

   Full updated item = ALL_NEW [OK]

Hint: Use ALL_NEW to get full updated item after update [OK]

Common Mistakes:

• Choosing UPDATED_OLD which returns old updated attributes
• Using NONE expecting data back
• Selecting ALL_OLD which returns old full item