Il pattern Orchestration Saga
Esplori l'approccio di tipo orchestration, in cui un servizio dedicato coordina i passaggi di una transazione distribuita.
Il pattern Orchestration Saga è una lezione Microservices Communication Patterns (Saga, Circuit Breaker) gratuita su CoddyKit. Questa è la lezione 3 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Microservices Communication Patterns (Saga, Circuit Breaker), e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Microservices Communication Patterns (Saga, Circuit Breaker) include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
Introducing Orchestration Sagas
Welcome to the Orchestration Saga! In a distributed system, sometimes a business transaction needs to involve multiple services.
An Orchestration Saga is a pattern where a central service, called an orchestrator, takes charge of guiding the entire transaction.
The Role of the Orchestrator
Think of the orchestrator as a project manager for your distributed transaction. It knows all the steps and coordinates them.
- It sends commands to participant services.
- It waits for responses (events) from those services.
- It decides the next step based on the responses.
How it Works: A Simple Flow
Unlike a Choreography Saga where services react to events from each other, here the orchestrator is in control:
- Orchestrator sends a command to Service A.
- Service A performs its task and sends a completion event back to the orchestrator.
- Orchestrator receives the event and sends a command to Service B.
- This continues until the transaction is complete.
Example: Online Order Process
Let's use an online order as an example. An order might need to:
- Create an order in the Order Service.
- Reserve items in the Inventory Service.
- Process payment in the Payment Service.
- Initiate shipping in the Shipping Service.
An orchestrator would manage this sequence.
Orchestrator's State Management
The orchestrator must keep track of the saga's current state and context. This means it needs to store information like:
- Which steps have completed?
- What data was returned by previous steps?
- What is the current status (e.g.,
PAYMENT_PENDING,INVENTORY_RESERVED)?
This state is crucial for deciding the next action or handling failures.
Commands & Events
The orchestrator communicates using two main types of messages:
- Commands: Sent from the orchestrator to a service, telling it what to do (e.g.,
ReserveInventory). - Events: Sent from a service back to the orchestrator, reporting the outcome (e.g.,
InventoryReserved,PaymentFailed).
This clear distinction helps maintain control.
Handling Failures & Compensation
What if a step fails? The orchestrator is responsible for compensation.
If the Payment Service fails, the orchestrator detects the PaymentFailed event. It then knows to send compensation commands to previous services, such as ReleaseInventory to the Inventory Service and CancelOrder to the Order Service.
Orchestrator Flow Demo
Let's look at a simplified Java example. This isn't a full microservice, but it shows how an orchestrator's logic might flow, reacting to simulated service outcomes.
Notice how it tracks sagaState and triggers compensation if payment fails.
public class OrderSagaOrchestrator {
public static void main(String[] args) {
System.out.println("Saga Orchestrator Started: Order 123");
String sagaState = "ORDER_INITIATED";
System.out.println("Orchestrator: Sending 'CREATE_ORDER' command.");
// Simulate Order Service success
sagaState = "ORDER_CREATED";
System.out.println("Orchestrator: Received 'ORDER_CREATED' event.");
if (sagaState.equals("ORDER_CREATED")) {
System.out.println("Orchestrator: Sending 'RESERVE_INVENTORY' command.");
// Simulate Inventory Service success
sagaState = "INVENTORY_RESERVED";
System.out.println("Orchestrator: Received 'INVENTORY_RESERVED' event.");
}
if (sagaState.equals("INVENTORY_RESERVED")) {
System.out.println("Orchestrator: Sending 'PROCESS_PAYMENT' command.");
// Simulate Payment Service *failure*
System.out.println("Orchestrator: Received 'PAYMENT_FAILED' event.");
sagaState = "PAYMENT_FAILED";
}
if (sagaState.equals("PAYMENT_FAILED")) {
System.out.println("Orchestrator: Initiating compensation!");
System.out.println("Orchestrator: Sending 'CANCEL_ORDER' command.");
System.out.println("Orchestrator: Sending 'RELEASE_INVENTORY' command.");
sagaState = "SAGA_COMPENSATED";
System.out.println("Orchestrator: Saga completed with compensation.");
} else {
System.out.println("Orchestrator: Sending 'CONFIRM_ORDER' command.");
System.out.println("Orchestrator: Sending 'SHIP_ORDER' command.");
sagaState = "SAGA_COMPLETED_SUCCESSFULLY";
System.out.println("Orchestrator: Saga completed successfully.");
}
}
}Advantages of Orchestration
Orchestration Sagas offer clear benefits:
- Centralized Control: Easier to understand the overall flow.
- Simplified Participant Services: Services don't need to know about the entire saga; they just follow orchestrator commands.
- Easier Debugging: The orchestrator's state makes it simpler to trace issues.
- Explicit Compensation: Compensation logic is clearly defined within the orchestrator.
Check Your Understanding
Which of the following statements accurately describe key characteristics of an Orchestration Saga?
Recap: Orchestration Saga
You've learned about the Orchestration Saga pattern!
- It uses a central orchestrator service to manage a distributed transaction.
- The orchestrator sends commands to services and receives events as responses.
- It maintains the saga's state to know where it is in the transaction.
- It explicitly handles compensation by issuing rollback commands if a step fails.
This pattern provides clear control and simplifies participant services.
Impara Microservices Communication Patterns (Saga, Circuit Breaker) con un tutor IA — gratis
Scrivi ed esegui vero codice nel tuo browser, ricevi aiuto istantaneo da un tutor IA disponibile 24/7, e riprendi da dove hai lasciato sul web o nell'app.
- Corsi
- 12
- Lezioni
- 48
Domande Frequenti
La lezione «Il pattern Orchestration Saga» è gratuita?
Sì — il testo completo di «Il pattern Orchestration Saga» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Microservices Communication Patterns (Saga, Circuit Breaker), passa a CoddyKit PRO. Il corso Microservices Communication Patterns (Saga, Circuit Breaker) include 4 lezioni in totale.
Cosa imparerò in «Il pattern Orchestration Saga»?
Esplori l'approccio di tipo orchestration, in cui un servizio dedicato coordina i passaggi di una transazione distribuita. Eserciti Microservices Communication Patterns (Saga, Circuit Breaker) con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare Microservices Communication Patterns (Saga, Circuit Breaker)?
Non è richiesta alcuna esperienza precedente. Microservices Communication Patterns (Saga, Circuit Breaker) su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 3 di 4.
Quanto tempo richiede la lezione «Il pattern Orchestration Saga»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione Microservices Communication Patterns (Saga, Circuit Breaker)?
Sì. Ogni lezione Microservices Communication Patterns (Saga, Circuit Breaker) include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Che cos'è il pattern Saga
- Il pattern Choreography Saga
- Il pattern Orchestration Saga
- Scegliere tra choreography e orchestration