Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Alibaba Exam ACA-CloudNative Topic 5 Question 103 Discussion

Actual exam question for Alibaba's ACA-CloudNative exam
Question #: 103
Topic #: 5
[All ACA-CloudNative Questions]

How to keep the data consistency in microservices architecture refer to microservice.io?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Janine
28 days ago
If Option D doesn't work, I guess we could always try Option E: Throw the whole thing out and go back to monoliths. Just kidding, but seriously, D is the way to go.
upvoted 0 times
Phyliss
10 hours ago
B) Database lock required (commit and rollback scenario)
upvoted 0 times
...
Phil
7 days ago
A) Use PL/SQL Statement from RDBMS
upvoted 0 times
...
...
Scarlet
1 months ago
D is the clear winner here. Who wants to deal with manual database locks and rollbacks when you can auMyate the whole process? Sign me up for the Choreographer and Event Bus!
upvoted 0 times
Chana
21 days ago
I agree, D is definitely the way to go. Automation is key in microservices architecture.
upvoted 0 times
...
...
My
1 months ago
Hmm, I was leaning towards C until I read the details on D. Encapsulating the failure handling in a Choreographer is a much cleaner solution than trying to coordinate it across the individual services.
upvoted 0 times
...
Eugene
2 months ago
I'm not sure about the other options, but D definitely sounds like the most comprehensive approach. Handling failures across multiple services can be tricky, so having a centralized way to manage that is key.
upvoted 0 times
Gail
20 days ago
I think so too. It provides a centralized way to handle failures and maintain consistency across services.
upvoted 0 times
...
Claribel
21 days ago
I agree, using a Choreographer and Event Bus seems like the best way to ensure data consistency in microservices architecture.
upvoted 0 times
...
...
Elouise
2 months ago
Option D seems like the way to go. Using a Choreographer and Event Bus to handle failed scenarios seems like a robust and flexible solution for maintaining data consistency in a microservices architecture.
upvoted 0 times
...
Milly
2 months ago
I prefer using store procedure/function from RDBMS for data consistency in microservices.
upvoted 0 times
...
Johnson
2 months ago
I agree with Penney, using an Event Bus can help in handling failed scenarios effectively.
upvoted 0 times
...
Penney
2 months ago
I think using a Choreographer and Event Bus is the best option to maintain data consistency in microservices.
upvoted 0 times
...

Save Cancel