Transaction error handling in DynamoDB - Mini Project: Build & Apply

Transaction Error Handling in DynamoDB

📖 Scenario: You are managing a simple inventory system where you need to update stock quantities for products. Sometimes, multiple updates happen at once, and you want to make sure either all updates succeed or none do, to keep data consistent.

🎯 Goal: Build a DynamoDB transaction that updates stock quantities for two products. Add error handling to catch transaction failures and handle them gracefully.

📋 What You'll Learn

Create a transaction with two update operations on the Products table

Use a condition expression to ensure stock quantity does not go below zero

Add error handling to catch TransactionCanceledException

Log or handle the error when the transaction fails

💡 Why This Matters

🌍 Real World

In real inventory systems, transactions ensure that stock updates happen safely without partial changes that could cause errors or inconsistencies.

💼 Career

Understanding transaction error handling in DynamoDB is important for backend developers and database administrators to maintain data integrity and build reliable applications.

1

Setup DynamoDB client and transaction parameters

Create a DynamoDB client called dynamodb using boto3.client('dynamodb'). Then create a variable called transaction_items that is a list containing two update operations. Each update should target the Products table and update the Stock attribute for products with ProductId 'A123' and 'B456' respectively. Use Update action with Key, UpdateExpression, and ExpressionAttributeValues to subtract 1 from Stock.

DynamoDB

import boto3

dynamodb = boto3.client('dynamodb')

# Create transaction_items list with two update operations
# Your code here

Hint

Use boto3.client('dynamodb') to create the client. For each update, specify the table name, key with product ID, update expression to subtract 1 from stock, and a condition expression to prevent stock from going below zero.

2

Add transaction configuration

Create a variable called transaction_params that is a dictionary with a key TransactItems set to the transaction_items list.

DynamoDB

import boto3

dynamodb = boto3.client('dynamodb')

transaction_items = [
    # existing update operations
]

# Create transaction_params dictionary with TransactItems key
# Your code here

Hint

Wrap the transaction_items list inside a dictionary with the key TransactItems.

3

Execute the transaction with error handling

Use a try block to call dynamodb.transact_write_items(**transaction_params). Add an except block to catch dynamodb.exceptions.TransactionCanceledException and assign the exception to a variable called e.

DynamoDB

import boto3

dynamodb = boto3.client('dynamodb')

transaction_items = [
    # existing update operations
]

transaction_params = {'TransactItems': transaction_items}

# Add try-except block to execute transaction and catch TransactionCanceledException
# Your code here

Hint

Use a try block to run the transaction. Catch TransactionCanceledException with except dynamodb.exceptions.TransactionCanceledException as e:.

4

Handle the transaction error

Inside the except block, add a line to assign the string 'Transaction failed' to a variable called error_message. This simulates handling the error.

DynamoDB

import boto3

dynamodb = boto3.client('dynamodb')

transaction_items = [
    # existing update operations
]

transaction_params = {'TransactItems': transaction_items}

try:
    dynamodb.transact_write_items(**transaction_params)
except dynamodb.exceptions.TransactionCanceledException as e:
    # Assign 'Transaction failed' to error_message variable
    # Your code here

Hint

Inside the except block, assign the string 'Transaction failed' to a variable named error_message.

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