Choreography
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
coordinate a saga through events only.
Planned topics
- Each service reacts to events and emits its own:
OrderPlaced→StockReserved→PaymentAuthorized. - No central owner, low coupling, easy for 2 to 3 steps.
- The process lives nowhere in code: it is hard to see, test, and change as it grows.
- Risk of cyclic dependencies and "who handles the failure?" confusion.
- Add a correlation id (order id) to every event for tracing.
Draft outline details
Demonstration
an event flow diagram: orders → inventory → payments → orders, with failure events PaymentDeclined flowing back.
Check your understanding
What is the main weakness of choreography as steps grow?
Show answer
The overall flow is implicit and hard to follow or change.
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.