Choreography Saga Explained
Understand the choreography approach where services communicate directly via events without a central coordinator.
Choreography Saga Explained is a free Microservices Communication Patterns (Saga, Circuit Breaker) lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Microservices Communication Patterns (Saga, Circuit Breaker) learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Choreography Saga Intro
Welcome! In this lesson, we'll explore the Choreography Saga pattern. It's a way to manage complex business transactions that span multiple services in a decentralized way.
Unlike an orchestra with a conductor, choreography is like a dance where each dancer knows their part and reacts to others' movements.
Decentralized Event Flow
In a choreography saga, there's no central coordinator service. Instead, each service involved in the transaction publishes events and listens for events from other services.
- Services react to events.
- They perform their part of the transaction.
- They publish new events to trigger the next step.
Order Processing Example
Let's use a common example: processing a customer order. This involves multiple steps across different services:
- Order Service: Creates the order.
- Payment Service: Handles payment.
- Inventory Service: Updates stock.
How do these services coordinate without a central brain?
Step 1: Order Created Event
When a customer places an order, the Order Service starts the saga. It saves the order and then publishes an OrderCreatedEvent.
This event signals to other services that a new order is ready for processing.
public class OrderService {
public static void processNewOrder(String orderId) {
System.out.println("Order Service: Received new order " + orderId);
System.out.println("Order Service: Saving order " + orderId + " to database...");
// Imagine database interaction here
System.out.println("Order Service: Order " + orderId + " saved.");
System.out.println("Order Service: Publishing 'OrderCreatedEvent' for " + orderId);
}
public static void main(String[] args) {
processNewOrder("ORD789"); // Simulate a new order coming in
}
}Step 2: Payment Service Reacts
The Payment Service is subscribed to OrderCreatedEvents. When it receives one, it processes the payment for that order.
After processing, it publishes either a PaymentProcessedEvent or a PaymentFailedEvent.
public class PaymentService {
public static void handleOrderCreated(String orderId) {
System.out.println("Payment Service: Received 'OrderCreatedEvent' for order " + orderId);
System.out.println("Payment Service: Processing payment for " + orderId + "...");
// Simulate payment gateway interaction
boolean paymentSuccess = true; // For this example, assume success
if (paymentSuccess) {
System.out.println("Payment Service: Payment successful for " + orderId + ".");
System.out.println("Payment Service: Publishing 'PaymentProcessedEvent' for " + orderId);
} else {
System.out.println("Payment Service: Payment failed for " + orderId + ".");
System.out.println("Payment Service: Publishing 'PaymentFailedEvent' for " + orderId);
}
}
public static void main(String[] args) {
handleOrderCreated("ORD789"); // Simulate receiving an event
}
}Step 3: Inventory Service Updates
Next, the Inventory Service listens for PaymentProcessedEvents. Upon receiving one, it reduces the stock for the ordered items.
It then publishes an InventoryUpdatedEvent to indicate its task is complete.
public class InventoryService {
public static void handlePaymentProcessed(String orderId) {
System.out.println("Inventory Service: Received 'PaymentProcessedEvent' for order " + orderId);
System.out.println("Inventory Service: Updating stock for order " + orderId + "...");
// Simulate inventory database update
System.out.println("Inventory Service: Stock updated for order " + orderId + ".");
System.out.println("Inventory Service: Publishing 'InventoryUpdatedEvent' for " + orderId);
}
public static void main(String[] args) {
handlePaymentProcessed("ORD789"); // Simulate receiving an event
}
}The Challenge of Failures
What happens if a step in this flow fails? For example, if the payment fails, we can't update inventory. We also need to undo any previous successful steps.
This is where compensation logic comes in. It's about reversing previously completed actions.
Compensation in Choreography
In a choreography saga, compensation also happens through events. If a service fails, it publishes a compensation event.
Other services listen for these compensation events and perform their own rollback actions.
Compensation Example: Payment Fails
Imagine the Payment Service fails and publishes a PaymentFailedEvent. The Order Service, which started the saga, listens for this event.
Upon receiving it, the Order Service updates the order status to 'Cancelled', effectively rolling back the transaction from its side.
public class OrderService {
public static void handlePaymentFailed(String orderId) {
System.out.println("Order Service: Received 'PaymentFailedEvent' for order " + orderId);
System.out.println("Order Service: Initiating compensation for " + orderId + ".");
// Change order status to 'Cancelled'
System.out.println("Order Service: Updating order " + orderId + " status to 'Cancelled'.");
// Could publish OrderCancelledEvent if other services need to know
}
public static void main(String[] args) {
handlePaymentFailed("ORD789"); // Simulate receiving a compensation event
}
}Pros and Cons of Choreography
Choreography offers benefits but also presents challenges:
- Pros: Highly decoupled services, no central point of failure, simpler to implement for simple flows.
- Cons: Can be harder to monitor the overall transaction flow, complex compensation logic, potential for 'event storms' if not designed carefully.
Choreography Check
Consider a choreography saga where an 'OrderConfirmedEvent' is published. Which statement accurately describes how the next step is initiated?
Recap: Choreography Saga
You've learned about the Choreography Saga pattern:
- It's a decentralized approach for distributed transactions.
- Services communicate by publishing and subscribing to events.
- There's no central coordinator; each service knows its role.
- Compensation for failures is also handled via events, allowing services to roll back their actions.
This pattern promotes loose coupling but requires careful design for monitoring and compensation.
Frequently asked questions
Is the “Choreography Saga Explained” lesson free?
Yes — the full text of “Choreography Saga Explained” is free to read here on the web, and the Microservices Communication Patterns (Saga, Circuit Breaker) course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Microservices Communication Patterns (Saga, Circuit Breaker) course, upgrade to CoddyKit PRO.
What will I learn in “Choreography Saga Explained”?
Understand the choreography approach where services communicate directly via events without a central coordinator. You practise Microservices Communication Patterns (Saga, Circuit Breaker) with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Microservices Communication Patterns (Saga, Circuit Breaker)?
No prior experience is required. Microservices Communication Patterns (Saga, Circuit Breaker) on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Choreography Saga Explained” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Microservices Communication Patterns (Saga, Circuit Breaker) lesson?
Yes. Every Microservices Communication Patterns (Saga, Circuit Breaker) lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- What is the Saga Pattern?
- Choreography Saga Explained
- Orchestration Saga Explained
- Choosing Between Choreography and Orchestration