Stream vs polling comparison in DynamoDB - Performance Comparison

Time Complexity: Stream vs polling comparison

O(n) for polling, O(k) for streams

Understanding Time Complexity

When working with DynamoDB, we often need to get updates from the database. Two common ways are streams and polling.

We want to understand how the time it takes to get updates changes as the amount of data grows.

Scenario Under Consideration

Analyze the time complexity of these two approaches.

// Polling example
while (true) {
  let results = dynamodb.scan({ TableName: 'MyTable' });
  process(results.Items);
  wait(5000); // wait 5 seconds
}

// Stream example
// DynamoDB Streams sends only new changes as events
onStreamEvent(event) {
  process(event.Records);
}
    

The polling code repeatedly scans the whole table every few seconds. The stream code processes only new changes as they happen.

Identify Repeating Operations

• Polling primary operation: Scanning the entire table repeatedly.
• Polling how many times: Every fixed interval, regardless of changes.
• Stream primary operation: Processing only new change records as they arrive.
• Stream how many times: Only when data changes happen.

How Execution Grows With Input

Compare how work grows as the table size or changes increase.

Input Size (n)	Polling Approx. Operations	Stream Approx. Operations
10 items	Scan 10 items every interval	Process only changed items
100 items	Scan 100 items every interval	Process only changed items
1000 items	Scan 1000 items every interval	Process only changed items

Pattern observation: Polling work grows with total table size each time. Stream work grows only with actual changes.

Final Time Complexity

Time Complexity: O(n) for polling, O(k) for streams where k is number of changes

Polling checks all data every time, so work grows with table size. Streams only handle new changes, so work grows with changes, not total data.

Common Mistake

[X] Wrong: "Polling is always faster because it's simpler and doesn't need setup."

[OK] Correct: Polling does more work as data grows, causing delays and higher cost. Streams handle only new data, making them more efficient for large or active tables.

Interview Connect

Understanding how data retrieval methods scale helps you design efficient systems. This skill shows you can think about real-world costs and performance, which is valuable in many jobs.

Self-Check

"What if the polling interval is increased to scan less often? How would that affect the time complexity and system responsiveness?"

Practice

1. Which of the following best describes DynamoDB Streams compared to polling?

easy

A. Polling and streams both check for changes only once a day.

B. Polling pushes data changes immediately, streams check periodically.

C. Streams push data changes immediately, polling checks periodically.

D. Both streams and polling push data changes immediately.

Solution

1. Step 1: Understand DynamoDB Streams behavior

   DynamoDB Streams send data change events as they happen, pushing updates immediately.

2. Step 2: Understand polling behavior

   Polling requires the client to ask for updates at fixed intervals, not instantly.

3. Final Answer:

   Streams push data changes immediately, polling checks periodically. -> Option C

4. Quick Check:

   Streams = push, Polling = periodic check [OK]

Hint: Streams push instantly; polling waits for your request [OK]

Common Mistakes:

• Confusing which method pushes data
• Thinking polling is real-time
• Assuming streams require manual checks

2. Which syntax correctly represents enabling DynamoDB Streams on a table using AWS CLI?

easy

A. aws dynamodb update-table --table-name MyTable --stream-specification StreamEnabled=true,StreamViewType=NEW_IMAGE

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

C. aws dynamodb create-stream --table-name MyTable --view NEW_IMAGE

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

Solution

1. Step 1: Identify correct AWS CLI command for streams

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

2. Step 2: Verify syntax correctness

   aws dynamodb update-table --table-name MyTable --stream-specification StreamEnabled=true,StreamViewType=NEW_IMAGE uses correct flags and parameters: StreamEnabled=true and StreamViewType=NEW_IMAGE.

3. Final Answer:

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

4. Quick Check:

   Enable streams with update-table and stream-specification [OK]

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

Common Mistakes:

• Using non-existent commands like create-stream
• Incorrect flag names
• Missing StreamEnabled parameter

3. Given a DynamoDB table with streams enabled, what will happen if you poll the table every 10 minutes instead of using streams?

medium

A. Polling disables streams temporarily.

B. You get real-time updates as soon as data changes.

C. Polling automatically triggers streams to push data.

D. You receive updates only every 10 minutes, possibly missing immediate changes.

Solution

1. Step 1: Understand polling frequency impact

   Polling every 10 minutes means updates are checked only at those intervals, not instantly.

2. Step 2: Compare with streams behavior

   Streams push changes immediately, so polling delays updates and may miss real-time events.

3. Final Answer:

   You receive updates only every 10 minutes, possibly missing immediate changes. -> Option D

4. Quick Check:

   Polling = delayed updates, not real-time [OK]

Hint: Polling delays updates; streams push instantly [OK]

Common Mistakes:

• Assuming polling is real-time
• Thinking polling triggers streams
• Believing polling disables streams

4. You wrote code to poll a DynamoDB table every 5 seconds but notice high latency and missed updates. What is the likely issue?

medium

A. Streams must be disabled to use polling.

B. Polling too frequently causes throttling and delays.

C. Polling automatically disables table writes.

D. Polling every 5 seconds guarantees no missed updates.

Solution

1. Step 1: Analyze polling frequency effects

   Polling very frequently can cause throttling or API limits, increasing latency.

2. Step 2: Understand polling limitations

   Polling does not guarantee no missed updates and can overload the system if too frequent.

3. Final Answer:

   Polling too frequently causes throttling and delays. -> Option B

4. Quick Check:

   Too frequent polling = throttling and latency [OK]

Hint: Avoid polling too often to prevent throttling [OK]

Common Mistakes:

• Thinking streams must be off to poll
• Believing polling disables writes
• Assuming frequent polling prevents missed updates

5. You need to build a dashboard that updates instantly when DynamoDB data changes. Which approach is best and why?

hard

A. Use DynamoDB Streams to push changes and update dashboard in real-time.

B. Poll the table every hour to reduce costs and update dashboard.

C. Disable streams and poll every 5 minutes for near real-time updates.

D. Use polling once a day and cache results for dashboard.

Solution

1. Step 1: Identify real-time update requirement

   The dashboard needs instant updates when data changes, requiring immediate notification.

2. Step 2: Compare streams and polling for real-time needs

   Streams push changes immediately, ideal for real-time dashboards; polling delays updates and is less efficient.

3. Final Answer:

   Use DynamoDB Streams to push changes and update dashboard in real-time. -> Option A

4. Quick Check:

   Real-time dashboard = use streams [OK]

Hint: For instant updates, prefer streams over polling [OK]

Common Mistakes:

• Choosing polling despite real-time need
• Ignoring cost vs latency trade-offs
• Assuming polling can be truly real-time