MENU
In a move toward using microservices, a company's management team has asked all development teams to build their services so that API requests depend only on that service's data store. One team is building a Payments service which has its own database; the service needs data that originates in the Accounts database. Both are using Amazon DynamoDB.
What approach will result in the simplest, decoupled, and reliable method to get near-real time updates from the Accounts database?
Suggested Answer: D
Get Premium DVA-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
37 comments · newest first
DO
Dottie
11 months ago
C is interesting, but I feel like it might not be as efficient as D.
GR
Graciela
11 months ago
Wait, can DynamoDB Streams really handle near-real time updates? Sounds too good to be true!
RA
Rachael
11 months ago
B could work too, but it adds complexity with caching.
DA
Daren
11 months ago
Not sure about that, A seems more reliable for ETL processes.
SE
Selene
12 months ago
I think D is the best choice. DynamoDB Streams are perfect for this!
DA
Dannette
12 months ago
I'm leaning towards DynamoDB Streams since it seems like the most straightforward way to get updates directly from the Accounts database without too much overhead.
BE
Bettyann
1 year ago
I practiced a similar question where we discussed caching strategies. I wonder if ElastiCache would be a good fit here, but it might not be as real-time as needed.
TO
Tonja
1 year ago
I think using AWS Glue for ETL might be too heavy for this scenario. It feels like it could introduce delays, right?
SU
Sunny
1 year ago
I remember studying about using DynamoDB Streams for real-time updates, but I'm not entirely sure how it compares to the other options.
TI
Timothy
1 year ago
I think I'm going to go with option C and use Data Firehose. That seems like it would provide a nice, decoupled way to get the data from Accounts into Payments.
AL
Alexis
1 year ago
Option D with DynamoDB Streams seems like it could work, but I'm not sure how reliable and low-latency that would be compared to the other options.
LU
Lucia
1 year ago
I'm leaning towards option B with ElastiCache. That way the Payments service can just query the cache without having to worry about the Accounts database directly.
LE
Leanna
1 year ago
Hmm, using DynamoDB Streams seems like it could be a good way to get near-real time updates, but I'm not sure if that's the simplest or most decoupled solution.
TI
Tiara
1 year ago
This looks like a tricky one. I'll need to think through the different options carefully to figure out the best approach.
CR
Cristy
2 years ago
Wow, using triggers in the Accounts database to update ElastiCache? Talk about an overly complex solution. D is the way to go, folks.
JA
Jacquelyne
2 years ago
No need to overcomplicate things with triggers and caches.
UL
Ula
2 years ago
It definitely simplifies the process and keeps things decoupled.
BR
Brice
2 years ago
Yeah, using DynamoDB Streams to deliver changes makes a lot of sense.
AN
Angelo
2 years ago
I agree, D seems like the simplest and most reliable option.
NI
Nicholle
2 years ago
I'm not sure, but I think option B could also work well by using ElastiCache to update the cache in Payments.
CL
Clarinda
2 years ago
I agree with Lenita, using DynamoDB Streams will ensure near-real time updates without the need for complex ETL processes.
BL
Blondell
2 years ago
Haha, who needs real-time updates when you can just have the Payments team call the Accounts team every time they need data? Option D is the way to go!
TA
Talia
2 years ago
Roxane: Exactly, it keeps everything streamlined and efficient.
LY
Lynette
2 years ago
User 3: It's definitely the most decoupled approach, no need for constant communication between teams.
RO
Roxane
2 years ago
User 2: I agree, using DynamoDB Streams seems like the simplest and most reliable method.
CE
Cecil
2 years ago
User 1: Option D is definitely the way to go. Real-time updates without bothering the Accounts team.
LE
Lenita
2 years ago
I think option D is the best choice because DynamoDB Streams can deliver real-time updates.
MA
Marge
2 years ago
For a microservices architecture, D is definitely the way to go. Elegant and efficient solution.
SA
Sarah
2 years ago
C) Use Amazon Data Firehose to deliver all changes from the Accounts database to the Payments database.
PO
Portia
2 years ago
Absolutely, DynamoDB Streams is the best choice for near-real time updates.
LA
Lashawnda
2 years ago
D) Use Amazon DynamoDB Streams to deliver all changes from the Accounts database to the Payments database.
WI
Wilda
2 years ago
I agree, DynamoDB Streams is the clear winner here. Much simpler than messing with ETL or caching.
TH
Theola
2 years ago
Option D all the way! Using DynamoDB Streams is the way to go for near-real time updates. Keeps things super decoupled and reliable.
AJ
Aja
2 years ago
I prefer the simplicity of using DynamoDB Streams for real-time updates.
ST
Stephane
2 years ago
I think using AWS Glue for ETL updates might introduce unnecessary complexity.
BL
Blythe
2 years ago
Yeah, DynamoDB Streams will definitely keep things decoupled and reliable.
MA
Marylin
2 years ago
I agree, Option D with DynamoDB Streams sounds like the best choice for near-real time updates.