Active-active and conflict handling
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
explain what active-active really requires.
Planned topics
- Every region serves writes, so concurrent updates to the same data can conflict.
- Strategies: partition data by home region, last-write-wins, merge types (CRDTs), or avoid conflicts by design.
- Latency and consistency trade-offs are permanent, not a one-time project.
- Often only some data needs it.
Draft outline details
Demonstration
an example: order is homed in a region; any region can read; writes route to the home region; stock uses regional pools instead of one global counter.
Check your understanding
What is the main extra problem in active-active?
Show answer
Conflicting concurrent writes in different regions.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.