Saga de orquestación explicada
Explore el enfoque de orquestación, en el que un servicio dedicado coordina los pasos de una transacción distribuida.
Saga de orquestación explicada es una lección gratuita de Microservices Communication Patterns (Saga, Circuit Breaker) en CoddyKit. Esta es la lección 3 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Microservices Communication Patterns (Saga, Circuit Breaker), y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Microservices Communication Patterns (Saga, Circuit Breaker) incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
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.
Aprende Microservices Communication Patterns (Saga, Circuit Breaker) con un tutor de IA — gratis
Escribe y ejecuta código real en tu navegador, obtén ayuda instantánea de un tutor de IA disponible 24/7 y continúa donde lo dejaste en la web o en la aplicación.
- Cursos
- 12
- Lecciones
- 48
Preguntas frecuentes
¿La lección «Saga de orquestación explicada» es gratis?
Sí — el texto completo de «Saga de orquestación explicada» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Microservices Communication Patterns (Saga, Circuit Breaker), actualiza a CoddyKit PRO. El curso de Microservices Communication Patterns (Saga, Circuit Breaker) incluye 4 lecciones en total.
¿Qué aprenderé en «Saga de orquestación explicada»?
Explore el enfoque de orquestación, en el que un servicio dedicado coordina los pasos de una transacción distribuida. Practicas Microservices Communication Patterns (Saga, Circuit Breaker) con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar Microservices Communication Patterns (Saga, Circuit Breaker)?
No se requiere experiencia previa. Microservices Communication Patterns (Saga, Circuit Breaker) en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 3 de 4.
¿Cuánto tiempo toma la lección «Saga de orquestación explicada»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de Microservices Communication Patterns (Saga, Circuit Breaker)?
Sí. Cada lección de Microservices Communication Patterns (Saga, Circuit Breaker) incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- ¿Qué es el patrón Saga?
- Saga de coreografía explicada
- Saga de orquestación explicada
- Elección entre coreografía y orquestación