Transaction conditions in DynamoDB

Introduction

Transaction conditions help make sure changes happen only if certain rules are true. This keeps your data safe and correct.

You want to update a user's balance only if they have enough money.

You want to add a new item only if it doesn't already exist.

You want to delete a record only if it matches a specific status.

You want to change multiple items together but only if all conditions are met.

You want to avoid conflicts when many people change data at the same time.

Syntax

DynamoDB

TransactWriteItems {
  TransactItems: [
    {
      Put: {
        TableName: "TableName",
        Item: { ... },
        ConditionExpression: "condition_expression"
      }
    },
    {
      Update: {
        TableName: "TableName",
        Key: { ... },
        UpdateExpression: "update_expression",
        ConditionExpression: "condition_expression"
      }
    }
    // More actions
  ]
}

ConditionExpression is a string that defines the rule to check before the action.

If any condition fails, the whole transaction stops and no changes happen.

Examples

This adds a new user only if the UserId does not already exist.

DynamoDB

TransactWriteItems {
  TransactItems: [
    {
      Put: {
        TableName: "Users",
        Item: { "UserId": "123", "Name": "Alice" },
        ConditionExpression: "attribute_not_exists(UserId)"
      }
    }
  ]
}

This subtracts 100 from Balance only if Balance is at least 100.

DynamoDB

TransactWriteItems {
  TransactItems: [
    {
      Update: {
        TableName: "Accounts",
        Key: { "AccountId": "abc" },
        UpdateExpression: "SET Balance = Balance - :amount",
        ConditionExpression: "Balance >= :amount",
        ExpressionAttributeValues: { ":amount": { "N": "100" } }
      }
    }
  ]
}

Sample Program

This transaction tries to add a new product p1 only if it doesn't exist, and reduce stock of product p2 by 5 only if it has enough stock.

DynamoDB

TransactWriteItems {
  TransactItems: [
    {
      Put: {
        TableName: "Inventory",
        Item: { "ProductId": "p1", "Stock": { "N": "10" } },
        ConditionExpression: "attribute_not_exists(ProductId)"
      }
    },
    {
      Update: {
        TableName: "Inventory",
        Key: { "ProductId": "p2" },
        UpdateExpression: "SET Stock = Stock - :qty",
        ConditionExpression: "Stock >= :qty",
        ExpressionAttributeValues: { ":qty": { "N": "5" } }
      }
    }
  ]
}

Important Notes

All actions in a transaction succeed or fail together.

Use ConditionExpression to prevent unwanted changes.

Remember to provide ExpressionAttributeValues when using placeholders like :qty.

Summary

Transaction conditions check rules before changing data.

If any condition fails, no changes happen.

This helps keep your data safe and consistent.

Practice

1. What is the main purpose of using ConditionCheck in a DynamoDB transaction?

easy

A. To ensure certain conditions are met before making changes to data

B. To speed up the transaction by skipping checks

C. To delete all items in a table

D. To create a backup of the database

Solution

1. Step 1: Understand ConditionCheck role

   ConditionCheck verifies if specified conditions are true before allowing a transaction to proceed.

2. Step 2: Recognize transaction safety

   If conditions fail, the transaction is aborted, preventing unwanted data changes.

3. Final Answer:

   To ensure certain conditions are met before making changes to data -> Option A

4. Quick Check:

   Transaction conditions = safety check [OK]

Hint: ConditionCheck = verify before change [OK]

Common Mistakes:

• Thinking ConditionCheck speeds up transactions
• Confusing ConditionCheck with data deletion
• Assuming ConditionCheck creates backups

2. Which of the following is the correct syntax snippet for a ConditionCheck in a DynamoDB transaction?

easy

A. "ConditionCheck": {"Key": {"Id": {"N": 123}}, "TableName": "MyTable", "ConditionExpression": "attribute_exists(Id)"}

B. "ConditionCheck": {"Key": {"Id": "123"}, "TableName": "MyTable", "ConditionExpression": "attribute_exists(Id)"}

C. "ConditionCheck": {"Key": {"Id": {"S": "123"}}, "TableName": "MyTable", "ConditionExpression": "attribute_exists(Id)"}

D. "ConditionCheck": {"Key": {"Id": {"S": 123}}, "TableName": "MyTable", "ConditionExpression": "attribute_exists(Id)"}

Solution

1. Step 1: Check key format for string type

   DynamoDB expects string values to be wrapped as {"S": "value"} in JSON.

2. Step 2: Validate ConditionExpression and TableName

   ConditionExpression uses attribute_exists correctly; TableName is properly specified.

3. Final Answer:

   "ConditionCheck": {"Key": {"Id": {"S": "123"}}, "TableName": "MyTable", "ConditionExpression": "attribute_exists(Id)"} -> Option C

4. Quick Check:

   Correct JSON key format = "ConditionCheck": {"Key": {"Id": {"S": "123"}}, "TableName": "MyTable", "ConditionExpression": "attribute_exists(Id)"} [OK]

Hint: Use {"S": "string"} for string keys in ConditionCheck [OK]

Common Mistakes:

• Omitting the type wrapper like {"S": ...}
• Using number type for string keys
• Passing raw values without quotes

3. Given this transaction snippet, what happens if the item with Id = '101' does not exist?

{
  "TransactItems": [
    {
      "ConditionCheck": {
        "TableName": "Orders",
        "Key": {"Id": {"S": "101"}},
        "ConditionExpression": "attribute_exists(Id)"
      }
    },
    {
      "Update": {
        "TableName": "Orders",
        "Key": {"Id": {"S": "101"}},
        "UpdateExpression": "SET Status = :s",
        "ExpressionAttributeValues": {":s": {"S": "Processed"}}
      }
    }
  ]
}

medium

A. The update runs anyway, creating a new item

B. The transaction partially updates the item

C. The transaction ignores the ConditionCheck and updates

D. The transaction fails and no update happens

Solution

1. Step 1: Understand ConditionCheck with attribute_exists

   The ConditionCheck requires the item with Id '101' to exist for the transaction to proceed.

2. Step 2: Analyze transaction behavior on condition failure

   If the item does not exist, the condition fails, so the entire transaction is aborted and no update occurs.

3. Final Answer:

   The transaction fails and no update happens -> Option D

4. Quick Check:

   Condition failure aborts transaction = The transaction fails and no update happens [OK]

Hint: ConditionCheck failure stops whole transaction [OK]

Common Mistakes:

• Assuming update creates new item on failure
• Thinking transaction partially applies changes
• Ignoring ConditionCheck effect

4. You wrote this transaction but it always fails with a validation error:

{
  "TransactItems": [
    {
      "ConditionCheck": {
        "TableName": "Users",
        "Key": {"UserId": {"N": "abc"}},
        "ConditionExpression": "attribute_exists(UserId)"
      }
    }
  ]
}

What is the most likely cause?

medium

A. ConditionExpression syntax is wrong

B. The key type is incorrect; 'abc' is not a number

C. TableName is misspelled

D. ConditionCheck cannot be used alone

Solution

1. Step 1: Check key type and value

   The key uses type "N" (number) but the value "abc" is not numeric, causing validation error.

2. Step 2: Confirm other parts are correct

   ConditionExpression and TableName syntax are valid; ConditionCheck can be used alone.

3. Final Answer:

   The key type is incorrect; 'abc' is not a number -> Option B

4. Quick Check:

   Key type must match value format [OK]

Hint: Match key type with value format [OK]

Common Mistakes:

• Using non-numeric string with number type
• Assuming ConditionExpression syntax error
• Thinking ConditionCheck needs other actions

5. You want to update a user's email only if their current email is exactly '[e-mail]'. Which transaction condition setup achieves this safely?

hard

A. Use a ConditionCheck with ConditionExpression 'Email = :oldEmail' before the update

B. Use an Update with ConditionExpression 'attribute_exists(Email)'

C. Use a ConditionCheck with ConditionExpression 'attribute_not_exists(Email)'

D. Update without any condition; trust the data is correct

Solution

1. Step 1: Identify condition to match exact current email

   The condition must check that Email equals '[e-mail]' before updating.

2. Step 2: Use ConditionCheck to verify before update

   ConditionCheck with 'Email = :oldEmail' ensures update only happens if current email matches.

3. Final Answer:

   Use a ConditionCheck with ConditionExpression 'Email = :oldEmail' before the update -> Option A

4. Quick Check:

   Exact match condition before update = Use a ConditionCheck with ConditionExpression 'Email = :oldEmail' before the update [OK]

Hint: Check exact value with ConditionCheck before update [OK]

Common Mistakes:

• Using attribute_exists instead of exact match
• Checking attribute_not_exists which is opposite
• Skipping condition and risking wrong update