Transaction error handling in DynamoDB

Introduction

Transaction error handling helps you manage problems when multiple database actions happen together. It keeps your data safe and correct.

When you want to update several items at once and need all updates to succeed or none at all.

When you want to avoid partial changes that can cause wrong or broken data.

When you want to catch and fix errors like conflicts or missing items during a transaction.

When you want to retry a transaction if it fails due to temporary issues.

When you want to log or alert about problems during database updates.

Syntax

DynamoDB

Use TransactWriteItems API with a try-catch block in your code.

Example in JavaScript:

try {
  await dynamodb.transactWrite(params).promise();
} catch (error) {
  // handle error here
}

Transactions in DynamoDB let you group multiple write operations that succeed or fail together.

Errors can happen due to condition check failures, conflicts, or capacity limits.

Examples

This example tries to add a user and update an account balance together. If either fails, no change happens.

DynamoDB

const params = {
  TransactItems: [
    {
      Put: {
        TableName: 'Users',
        Item: { UserId: '123', Name: 'Alice' }
      }
    },
    {
      Update: {
        TableName: 'Accounts',
        Key: { AccountId: 'abc' },
        UpdateExpression: 'SET Balance = Balance - :amount',
        ExpressionAttributeValues: { ':amount': 100 }
      }
    }
  ]
};

try {
  await dynamodb.transactWrite(params).promise();
  console.log('Transaction succeeded');
} catch (error) {
  console.error('Transaction failed:', error.message);
}

This shows how to check the error type to handle specific transaction errors differently.

DynamoDB

try {
  await dynamodb.transactWrite(params).promise();
} catch (error) {
  if (error.code === 'TransactionCanceledException') {
    console.log('Transaction canceled due to condition failure or conflict');
  } else {
    console.log('Other error:', error.message);
  }
}

Sample Program

This program tries to add a product and reduce inventory stock by 5 in one transaction. If stock is less than 5, the transaction fails and prints a message.

DynamoDB

const AWS = require('aws-sdk');
const dynamodb = new AWS.DynamoDB.DocumentClient();

const params = {
  TransactItems: [
    {
      Put: {
        TableName: 'Products',
        Item: { ProductId: 'p1', Name: 'Pen', Stock: 10 }
      }
    },
    {
      Update: {
        TableName: 'Inventory',
        Key: { ItemId: 'p1' },
        UpdateExpression: 'SET Quantity = Quantity - :qty',
        ConditionExpression: 'Quantity >= :qty',
        ExpressionAttributeValues: { ':qty': 5 }
      }
    }
  ]
};

(async () => {
  try {
    await dynamodb.transactWrite(params).promise();
    console.log('Transaction succeeded');
  } catch (error) {
    if (error.code === 'TransactionCanceledException') {
      console.log('Transaction failed: Not enough stock or condition failed');
    } else {
      console.log('Transaction failed:', error.message);
    }
  }
})();

Important Notes

Always check error codes to understand why a transaction failed.

Use ConditionExpression to prevent unwanted updates during transactions.

Remember that all operations in a transaction must be in the same AWS region.

Summary

Transaction error handling keeps your data safe by making sure all changes happen together or not at all.

Use try-catch blocks to catch errors and respond properly.

Check error codes like TransactionCanceledException to know why a transaction failed.

Practice

1. What is the main purpose of transaction error handling in DynamoDB?

easy

A. To ensure all changes in a transaction happen together or not at all

B. To speed up query performance

C. To allow partial updates in a transaction

D. To automatically backup data after each transaction

Solution

1. Step 1: Understand transaction atomicity

   Transactions in DynamoDB ensure that either all operations succeed or none do, preventing partial updates.

2. Step 2: Identify the role of error handling

   Error handling detects when a transaction fails and prevents inconsistent data states.

3. Final Answer:

   To ensure all changes in a transaction happen together or not at all -> Option A

4. Quick Check:

   Transaction atomicity = To ensure all changes in a transaction happen together or not at all [OK]

Hint: Remember: transactions are all-or-nothing operations [OK]

Common Mistakes:

• Thinking transactions allow partial success
• Confusing error handling with performance tuning
• Assuming automatic backups happen on errors

2. Which of the following is the correct way to catch a transaction error in DynamoDB using JavaScript?

easy

A. try { await client.transactWrite(params); } catch (error) { if (error.code === 'TransactionCanceledException') { /* handle */ } }

B. await client.transactWrite(params).catch(error => if error.code == 'TransactionCanceledException' { /* handle */ })

C. try { client.transactWrite(params); } catch error { if error.code = 'TransactionCanceledException' { /* handle */ } }

D. client.transactWrite(params).then().catch(error => if (error.code === 'TransactionCanceledException') { /* handle */ })

Solution

1. Step 1: Check syntax for try-catch with async/await

   try { await client.transactWrite(params); } catch (error) { if (error.code === 'TransactionCanceledException') { /* handle */ } } correctly uses try-catch with await and compares error.code with 'TransactionCanceledException'.

2. Step 2: Identify syntax errors in other options

   await client.transactWrite(params).catch(error => if error.code == 'TransactionCanceledException' { /* handle */ }) has incorrect arrow function syntax; try { client.transactWrite(params); } catch error { if error.code = 'TransactionCanceledException' { /* handle */ } } misses parentheses and uses wrong assignment; client.transactWrite(params).then().catch(error => if (error.code === 'TransactionCanceledException') { /* handle */ }) uses then() without await which is less clear.

3. Final Answer:

   try { await client.transactWrite(params); } catch (error) { if (error.code === 'TransactionCanceledException') { /* handle */ } } -> Option A

4. Quick Check:

   Correct try-catch syntax = try { await client.transactWrite(params); } catch (error) { if (error.code === 'TransactionCanceledException') { /* handle */ } } [OK]

Hint: Use try-catch with await and check error.code string [OK]

Common Mistakes:

• Missing parentheses in catch block
• Using assignment '=' instead of comparison '==='
• Incorrect arrow function syntax in catch

3. Given this code snippet, what will be the output if the transaction fails due to a conditional check failure?

try {
  await client.transactWrite(params);
  console.log('Transaction succeeded');
} catch (error) {
  if (error.code === 'TransactionCanceledException') {
    console.log('Transaction failed: ' + error.message);
  } else {
    console.log('Other error');
  }
}

medium

A. Other error

B. Transaction succeeded

C. Transaction failed: ConditionalCheckFailed

D. No output

Solution

1. Step 1: Understand error handling flow

   If the transaction fails due to a conditional check, DynamoDB throws TransactionCanceledException with a message indicating ConditionalCheckFailed.

2. Step 2: Trace the catch block output

   The catch block checks error.code and prints 'Transaction failed: ' plus the error message, so it outputs the failure message.

3. Final Answer:

   Transaction failed: ConditionalCheckFailed -> Option C

4. Quick Check:

   Error code check prints failure message = Transaction failed: ConditionalCheckFailed [OK]

Hint: TransactionCanceledException means failure message logs [OK]

Common Mistakes:

• Assuming success message prints on failure
• Ignoring error.code check
• Confusing error messages with other exceptions

4. Identify the error in this DynamoDB transaction error handling code snippet:

try {
  client.transactWrite(params);
} catch (error) {
  if (error.code === 'TransactionCanceledException') {
    console.log('Transaction failed');
  }
}

medium

A. Try block should not be used with transactWrite

B. Incorrect error code string in if condition

C. Using console.log inside catch is invalid

D. Missing await before client.transactWrite causing unhandled promise

Solution

1. Step 1: Check async call handling

   client.transactWrite returns a promise; without await, errors won't be caught by try-catch.

2. Step 2: Confirm error handling correctness

   The error code string and console.log usage are correct; try-catch is valid for async with await.

3. Final Answer:

   Missing await before client.transactWrite causing unhandled promise -> Option D

4. Quick Check:

   Async calls need await for try-catch to work [OK]

Hint: Always await async calls inside try to catch errors [OK]

Common Mistakes:

• Omitting await on async functions
• Misnaming error codes
• Thinking console.log is disallowed in catch

5. You want to retry a DynamoDB transaction only if it fails due to a TransactionCanceledException caused by a conditional check failure. Which approach correctly implements this retry logic?

hard

A. Use try-catch but do not check error code; retry only once

B. Use a loop with try-catch; inside catch, check if error.code is 'TransactionCanceledException' and error.message contains 'ConditionalCheckFailed', then retry up to max attempts

C. Retry unconditionally on any error without checking error type

D. Ignore errors and assume transaction will succeed eventually

Solution

1. Step 1: Understand selective retry conditions

   Retry should happen only if error.code is 'TransactionCanceledException' and message indicates conditional check failure.

2. Step 2: Implement retry with loop and max attempts

   Use a loop with try-catch, check error details, and retry up to a limit to avoid infinite loops.

3. Final Answer:

   Use a loop with try-catch; inside catch, check if error.code is 'TransactionCanceledException' and error.message contains 'ConditionalCheckFailed', then retry up to max attempts -> Option B

4. Quick Check:

   Retry only on specific error with loop and checks = Use a loop with try-catch; inside catch, check if error.code is 'TransactionCanceledException' and error.message contains 'ConditionalCheckFailed', then retry up to max attempts [OK]

Hint: Retry only on specific error codes and messages [OK]

Common Mistakes:

• Retrying on all errors causing infinite loops
• Not checking error.message for conditional failure
• Ignoring max retry limits