Microservices - CI/CD for Microservices
In a microservices system using event sourcing, what rollback strategy best ensures data consistency after a faulty deployment?
In a microservices system using event sourcing, what rollback strategy best ensures data consistency after a faulty deployment?
hard📝 Trade-off Q9 of 15
Step-by-Step Solution
Solution:
Step 1: Understand event sourcing rollback
Event sourcing stores state as events; rollback means replaying events to a stable point.Step 2: Identify best rollback method
Replaying events up to last good state restores consistency without data loss.Final Answer:
Replay events up to the last known good state -> Option BQuick Check:
Event sourcing rollback = replay events [OK]
Quick Trick: Replay events to rollback in event sourcing [OK]
Common Mistakes:
- Deleting all events causing data loss
- Ignoring event data during rollback
- Rolling back code only without data consistency
Master "CI/CD for Microservices" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes