Event-driven architecture patterns in DynamoDB - Time & Space Complexity

Time Complexity: Event-driven architecture patterns

O(n)

Understanding Time Complexity

When using event-driven patterns with DynamoDB, it is important to understand how the time to process events grows as more events occur.

We want to know how the number of operations changes as the event load increases.

Scenario Under Consideration

Analyze the time complexity of the following DynamoDB event processing snippet.

// Assume events is a list of event records
for event in events:
  # Extract key from event
  key = event['key']
  # Query DynamoDB for item with key
  response = dynamodb.get_item(TableName='MyTable', Key={'id': {'S': key}})
  # Process the item
  process(response['Item'])
    

This code loops over each event and fetches the related item from DynamoDB to process it.

Identify Repeating Operations

Look at what repeats as the input grows.

• Primary operation: Looping over each event and performing a get_item call.
• How many times: Once per event in the events list.

How Execution Grows With Input

As the number of events increases, the number of get_item calls grows the same way.

Input Size (n)	Approx. Operations
10	10 get_item calls
100	100 get_item calls
1000	1000 get_item calls

Pattern observation: The work grows directly with the number of events.

Final Time Complexity

Time Complexity: O(n)

This means the time to process events grows linearly as more events come in.

Common Mistake

[X] Wrong: "Fetching one item from DynamoDB is slow, so processing many events is always slow regardless of approach."

[OK] Correct: Each get_item call is fast and independent, so total time depends mostly on how many events you process, not on hidden loops inside DynamoDB.

Interview Connect

Understanding how event-driven processing scales helps you design systems that handle growing workloads smoothly.

Self-Check

"What if we batch multiple keys in one DynamoDB request instead of one get_item per event? How would the time complexity change?"

Practice

1. What is the main purpose of using DynamoDB Streams in an event-driven architecture?

easy

A. To capture and record changes in the DynamoDB table as events

B. To store backup copies of the DynamoDB table

C. To increase the read capacity of the DynamoDB table

D. To encrypt data stored in DynamoDB

Solution

1. Step 1: Understand DynamoDB Streams role

   DynamoDB Streams capture data modification events like inserts, updates, and deletes.

2. Step 2: Identify the purpose in event-driven architecture

   These captured events trigger other processes automatically, enabling real-time reactions.

3. Final Answer:

   To capture and record changes in the DynamoDB table as events -> Option A

4. Quick Check:

   DynamoDB Streams = capture changes [OK]

Hint: Streams capture table changes as events for triggers [OK]

Common Mistakes:

• Confusing Streams with backups
• Thinking Streams increase capacity
• Assuming Streams encrypt data

2. Which of the following is the correct way to enable DynamoDB Streams on a table using AWS CLI?

easy

A. aws dynamodb set-stream --table MyTable --enabled true

B. aws dynamodb enable-stream --table MyTable --type NEW_IMAGE

C. aws dynamodb create-stream --table-name MyTable --view-type KEYS_ONLY

D. aws dynamodb update-table --table-name MyTable --stream-specification StreamEnabled=true,StreamViewType=NEW_AND_OLD_IMAGES

Solution

1. Step 1: Recall AWS CLI command for enabling streams

   The correct command uses 'update-table' with '--stream-specification' to enable streams.

2. Step 2: Verify syntax and parameters

   aws dynamodb update-table --table-name MyTable --stream-specification StreamEnabled=true,StreamViewType=NEW_AND_OLD_IMAGES correctly sets StreamEnabled=true and specifies StreamViewType as NEW_AND_OLD_IMAGES.

3. Final Answer:

   aws dynamodb update-table --table-name MyTable --stream-specification StreamEnabled=true,StreamViewType=NEW_AND_OLD_IMAGES -> Option D

4. Quick Check:

   Enable streams = update-table + stream-specification [OK]

Hint: Use update-table with stream-specification to enable streams [OK]

Common Mistakes:

• Using non-existent commands like enable-stream
• Incorrect parameter names
• Confusing create-stream with enabling streams

3. Given a DynamoDB Stream enabled with StreamViewType=NEW_IMAGE, what will an AWS Lambda function receive when an item is updated?

medium

A. Only the keys of the updated item

B. The entire item before and after the update

C. Only the new version of the item after the update

D. No data, only a notification that an update occurred

Solution

1. Step 1: Understand StreamViewType NEW_IMAGE meaning

   NEW_IMAGE sends only the new version of the item after the change.

2. Step 2: Determine what Lambda receives on update

   Lambda gets the updated item data, not the old version or just keys.

3. Final Answer:

   Only the new version of the item after the update -> Option C

4. Quick Check:

   NEW_IMAGE = new item data only [OK]

Hint: NEW_IMAGE sends only updated item data to Lambda [OK]

Common Mistakes:

• Confusing NEW_IMAGE with NEW_AND_OLD_IMAGES
• Assuming keys only are sent
• Thinking Lambda gets no data

4. You wrote a Lambda function triggered by DynamoDB Streams but it never executes. What is the most likely cause?

medium

A. The DynamoDB table does not have Streams enabled

B. The Lambda function is not subscribed to the stream

C. The Lambda function code has syntax errors

D. The DynamoDB table has no data

Solution

1. Step 1: Check if Streams are enabled

   If Streams were not enabled, no events would be generated, but question implies setup.

2. Step 2: Verify Lambda subscription to the stream

   Without subscribing Lambda to the stream, it won't trigger on events.

3. Final Answer:

   The Lambda function is not subscribed to the stream -> Option B

4. Quick Check:

   Lambda must be subscribed to stream to trigger [OK]

Hint: Ensure Lambda is subscribed to DynamoDB Stream [OK]

Common Mistakes:

• Assuming syntax errors stop invocation
• Thinking empty table stops Lambda trigger
• Ignoring subscription setup

5. You want to build a real-time notification system using DynamoDB and Lambda. Which event-driven architecture pattern best fits this use case?

hard

A. Use DynamoDB Streams to capture changes and trigger Lambda to send notifications

B. Use periodic polling of DynamoDB to check for changes and send notifications

C. Use DynamoDB Global Tables to replicate data and notify users

D. Use DynamoDB backups to trigger notifications on data changes

Solution

1. Step 1: Identify real-time event-driven pattern

   Real-time notifications require immediate reaction to data changes.

2. Step 2: Match pattern with DynamoDB Streams and Lambda

   Streams capture changes as events; Lambda processes them instantly to notify users.

3. Final Answer:

   Use DynamoDB Streams to capture changes and trigger Lambda to send notifications -> Option A

4. Quick Check:

   Streams + Lambda = real-time notifications [OK]

Hint: Streams trigger Lambda for instant notifications [OK]

Common Mistakes:

• Choosing polling which is not real-time
• Confusing replication with notifications
• Using backups which are not event triggers