Stream vs polling comparison in DynamoDB - Quick Revision & Key Differences

Recall & Review

beginner

What is DynamoDB Streams?

DynamoDB Streams is a feature that captures table activity in real-time and provides a time-ordered sequence of item-level changes.

beginner

How does polling work in DynamoDB?

Polling means repeatedly checking the table or a data source at intervals to see if there are any changes or new data.

intermediate

What is a key advantage of using DynamoDB Streams over polling?

Streams provide near real-time updates without the need to repeatedly check the database, saving resources and reducing latency.

intermediate

What is a disadvantage of polling compared to streams?

Polling can cause unnecessary load and delays because it checks for changes even when there are none, leading to wasted resources.

intermediate

When might polling be preferred over streams in DynamoDB?

Polling might be preferred if you want simple implementation without managing stream consumers or if near real-time updates are not critical.

What does DynamoDB Streams provide?

A A real-time sequence of data changes

B A way to backup data

C A method to delete data automatically

D A tool to create tables

DynamoDB Streams captures and provides a real-time sequence of item-level changes.

Which method repeatedly checks for data changes at intervals?

A Polling

B Caching

C Indexing

D Streaming

Polling means checking the data source repeatedly at set intervals.

What is a main benefit of using streams over polling?

A Works without internet

B Simpler to implement

C Lower latency and resource use

D Automatically deletes old data

Streams provide near real-time updates and reduce unnecessary resource use.

What is a downside of polling?

A It does not support updates

B It requires complex setup

C It only works with small tables

D It can cause unnecessary load

Polling can waste resources by checking for changes even when none exist.

When might polling be a better choice?

A When you need real-time updates

B When you want to avoid managing streams

C When you want to reduce load

D When you want automatic backups

Polling is simpler and may be preferred if managing streams is not desired.

Explain the difference between DynamoDB Streams and polling.

Think about how data changes are detected and how often.

Describe scenarios where you would choose polling over streams in DynamoDB.

Consider ease of setup and update speed needs.

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