BatchWriteItem in DynamoDB - Step-by-Step Execution

Concept Flow - BatchWriteItem

Prepare batch request with multiple Put/Delete

↓

Send BatchWriteItem request to DynamoDB

↓

DynamoDB processes items

↓

Check for UnprocessedItems

↓

Retry UnprocessedItems

BatchWriteItem sends multiple write requests at once. DynamoDB processes them and may return unprocessed items to retry.

Execution Sample

DynamoDB

BatchWriteItem({
  RequestItems: {
    'Table1': [
      { PutRequest: { Item: { id: '1', name: 'A' } } },
      { DeleteRequest: { Key: { id: '2' } } }
    ]
  }
})

This batch request writes one new item and deletes another in Table1.

Execution Table

Step	Action	Items Sent	DynamoDB Response	Next Step
1	Send BatchWriteItem request	Put id=1, Delete id=2	Processed both items	No UnprocessedItems, finish
2	Finish	-	-	Batch write complete

💡 All items processed successfully, no retries needed

Variable Tracker

Variable	Start	After Step 1	Final
RequestItems	{Put id=1, Delete id=2}	Sent to DynamoDB	No UnprocessedItems
UnprocessedItems	{}	{}	{}

Key Moments - 2 Insights

Why do we check for UnprocessedItems after sending the batch?

Because DynamoDB might not process all items in one go due to limits. The execution_table row 1 shows checking UnprocessedItems to decide if retry is needed.

Can BatchWriteItem mix Put and Delete requests?

Yes, as shown in the execution_sample code and execution_table row 1, both PutRequest and DeleteRequest can be in the same batch.

Visual Quiz - 3 Questions

Look at the execution_table, what happens if there are UnprocessedItems after the first request?

A The operation fails immediately

B The entire batch is resent

C The client retries sending only the unprocessed items

D DynamoDB processes unprocessed items automatically

💡 Hint

Refer to concept_flow where UnprocessedItems lead to retry of only those items

According to variable_tracker, what is the state of UnprocessedItems after step 1 in this example?

A Empty object, no retries needed

B Contains items to retry

C Undefined

D Contains all original items

💡 Hint

Check variable_tracker row for UnprocessedItems after Step 1

If we add more items than DynamoDB can process at once, what will the execution_table show?

A UnprocessedItems will be empty

B Some items will appear in UnprocessedItems to retry

C DynamoDB will process all items without issue

D BatchWriteItem will reject the request

💡 Hint

Recall concept_flow and key_moments about retrying unprocessed items

Concept Snapshot

BatchWriteItem lets you write or delete multiple items in one request.
You send a batch of PutRequest and DeleteRequest objects.
DynamoDB may return UnprocessedItems if it can't handle all at once.
You must retry only those unprocessed items.
This improves efficiency over single writes.

Full Transcript

BatchWriteItem is a DynamoDB operation to write or delete multiple items in one request. You prepare a batch with PutRequest and DeleteRequest objects for your table. When you send this batch, DynamoDB tries to process all items. Sometimes, due to limits, some items are not processed and returned as UnprocessedItems. You check for these and retry only those items. This process repeats until all items are processed or you decide to stop. This method is efficient because it reduces the number of requests compared to writing items one by one.

Practice

1.

What is the main purpose of the BatchWriteItem operation in DynamoDB?

easy

A. To create a new table in DynamoDB

B. To read multiple items from different tables

C. To add or delete multiple items in a single request

D. To update a single item with new attributes

Solution

1. Step 1: Understand BatchWriteItem functionality

   The BatchWriteItem operation allows you to write (add or delete) multiple items in one request to save time and reduce network calls.

2. Step 2: Compare options with BatchWriteItem purpose

   Only To add or delete multiple items in a single request correctly describes adding or deleting multiple items in one request, which matches BatchWriteItem's purpose.

3. Final Answer:

   To add or delete multiple items in a single request -> Option C

4. Quick Check:

   BatchWriteItem = add/delete many items [OK]

Hint: BatchWriteItem = batch add or delete items [OK]

Common Mistakes:

• Confusing BatchWriteItem with BatchGetItem
• Thinking it updates items instead of add/delete
• Assuming it creates tables

2.

Which of the following is the correct structure for a BatchWriteItem request in DynamoDB?

{
  "RequestItems": {
    "TableName": [
      { "PutRequest": { "Item": { ... } } },
      { "DeleteRequest": { "Key": { ... } } }
    ]
  }
}

easy

A. RequestItems is an array of table names with PutRequest and DeleteRequest inside

B. RequestItems contains table names as keys and arrays of PutRequest or DeleteRequest objects as values

C. RequestItems is a list of items without specifying table names

D. RequestItems only accepts PutRequest objects, not DeleteRequest

Solution

1. Step 1: Review BatchWriteItem request format

   The RequestItems key maps table names to arrays of write requests, each being either PutRequest or DeleteRequest.

2. Step 2: Match options to correct format

   RequestItems contains table names as keys and arrays of PutRequest or DeleteRequest objects as values correctly describes the structure: table names as keys, arrays of PutRequest/DeleteRequest as values.

3. Final Answer:

   RequestItems contains table names as keys and arrays of PutRequest or DeleteRequest objects as values -> Option B

4. Quick Check:

   RequestItems = table name keys + Put/Delete arrays [OK]

Hint: RequestItems keys are table names with Put/Delete arrays [OK]

Common Mistakes:

• Using array of table names instead of object with table keys
• Omitting DeleteRequest option
• Not nesting PutRequest/DeleteRequest inside arrays

3.

Given the following BatchWriteItem request, what will be the result if one item fails due to exceeding provisioned throughput?

{
  "RequestItems": {
    "Products": [
      { "PutRequest": { "Item": { "ID": { "S": "101" }, "Name": { "S": "Pen" } } } },
      { "PutRequest": { "Item": { "ID": { "S": "102" }, "Name": { "S": "Notebook" } } } }
    ]
  }
}

medium

A. The entire batch fails and no items are written

B. The request throws a syntax error

C. Both items are written regardless of failure

D. Only the failed item is returned in UnprocessedItems for retry

Solution

1. Step 1: Understand BatchWriteItem error handling

   If some items exceed provisioned throughput, DynamoDB returns those items in UnprocessedItems for retry, not failing the entire batch.

2. Step 2: Analyze the given scenario

   One item fails due to throughput, so only that item is unprocessed and returned for retry, while others succeed.

3. Final Answer:

   Only the failed item is returned in UnprocessedItems for retry -> Option D

4. Quick Check:

   UnprocessedItems = failed items for retry [OK]

Hint: Failed items appear in UnprocessedItems for retry [OK]

Common Mistakes:

• Assuming all items fail if one fails
• Thinking BatchWriteItem throws syntax error on throughput issues
• Believing all items succeed regardless of errors

4.

Identify the error in this BatchWriteItem request snippet:

{
  "RequestItems": {
    "Orders": [
      { "PutRequest": { "Item": { "OrderId": "123", "Amount": 50 } } }
    ]
  }
}

medium

A. The attribute values are missing DynamoDB data types

B. The table name should be an array, not an object

C. PutRequest should be outside the array

D. BatchWriteItem cannot write to Orders table

Solution

1. Step 1: Check attribute value format in BatchWriteItem

   DynamoDB requires attribute values to specify data types like {"S": "string"} or {"N": "number"} in BatchWriteItem requests.

2. Step 2: Identify the error in the snippet

   Attributes "OrderId" and "Amount" lack data type wrappers, so the request is invalid.

3. Final Answer:

   The attribute values are missing DynamoDB data types -> Option A

4. Quick Check:

   Attribute values need data types like {"S": "text"} [OK]

Hint: Attribute values must include DynamoDB data types [OK]

Common Mistakes:

• Omitting data types for attribute values
• Misunderstanding table name structure
• Placing PutRequest incorrectly

5.

You want to write 50 items to a DynamoDB table using BatchWriteItem. Since the API limits 25 items per batch, how should you handle this in your application?

hard

A. Split the 50 items into two batches of 25 and retry unprocessed items after each batch

B. Send all 50 items in one BatchWriteItem request and expect it to succeed

C. Write items one by one using PutItem to avoid batch limits

D. Use BatchGetItem instead to write multiple items

Solution

1. Step 1: Recognize BatchWriteItem limits

   BatchWriteItem supports a maximum of 25 items per request, so 50 items must be split into multiple batches.

2. Step 2: Implement batching and retry logic

   Split 50 items into two batches of 25 each. After each batch, check UnprocessedItems and retry those to ensure all items are written.

3. Final Answer:

   Split the 50 items into two batches of 25 and retry unprocessed items after each batch -> Option A

4. Quick Check:

   BatchWriteItem max 25 items; split and retry [OK]

Hint: Split items into max 25 per batch and retry unprocessed [OK]

Common Mistakes:

• Sending more than 25 items in one batch
• Ignoring unprocessed items and not retrying
• Using BatchGetItem to write items