Conceção de orquestradores Saga
Aprenda a conceber um serviço orquestrador dedicado, responsável por gerir o estado e as etapas de uma Saga.
Conceção de orquestradores Saga é uma aula grátis de Microservices Communication Patterns (Saga, Circuit Breaker) no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Microservices Communication Patterns (Saga, Circuit Breaker), e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Microservices Communication Patterns (Saga, Circuit Breaker) inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
What is a Saga Orchestrator?
In an Orchestration Saga, a dedicated service, called the Orchestrator, takes charge of managing the entire distributed transaction.
Think of it as a conductor in an orchestra. Instead of individual musicians (services) reacting to each other, the conductor (orchestrator) tells each musician when to play their part.
Why Use an Orchestrator?
Orchestration offers several advantages, especially for complex business flows:
- Centralized Logic: All saga logic resides in one place, making it easier to understand and manage.
- Easier Changes: Modifying saga steps or adding new ones is simpler as changes are contained within the orchestrator.
- Clearer Debugging: It's easier to trace the flow of a transaction and pinpoint exactly where a failure occurred.
Core Responsibilities
A saga orchestrator has crucial responsibilities to ensure the transaction completes successfully or is properly compensated:
- Initiates Saga: Starts the transaction by sending the first command.
- Tracks State: Maintains the current progress and state of the saga.
- Coordinates Steps: Sends commands to participant services based on the current state and responses.
- Handles Compensation: Triggers rollback actions if any step fails.
Example: Order Placement Saga
Let's consider an 'Order Placement' saga involving multiple services:
- Order Service: Creates the order.
- Payment Service: Processes the payment.
- Inventory Service: Updates stock.
- Shipping Service: Arranges delivery.
The orchestrator will guide the order through these steps.
Orchestrator State Management
The orchestrator must keep track of where the saga is in its lifecycle. This is its state. It typically stores:
sagaId: A unique identifier for the current transaction.currentStep: Which step is currently active or has been completed.status: e.g.,IN_PROGRESS,COMPLETED,FAILED,COMPENSATING.
This state must be persisted (saved) so the orchestrator can recover if it crashes.
Designing the Flow
The orchestrator's design centers around a state machine-like flow:
- Orchestrator sends a command to a participant service (e.g., 'ProcessPayment').
- Participant service performs its action and sends an event back (e.g., 'PaymentProcessed' or 'PaymentFailed').
- Orchestrator receives the event, updates its state, and decides the next command to send, or initiates compensation.
Orchestrator Structure (Code)
Here's a simplified Java example showing how an orchestrator might manage its state and react to responses. This code simulates the flow:
public class OrderSagaOrchestrator {
private String sagaId;
private String currentState;
public OrderSagaOrchestrator(String id) {
this.sagaId = id;
this.currentState = "INITIATED";
System.out.println("Saga " + sagaId + " state: " + currentState);
}
public void startOrderSaga() {
System.out.println("Sending 'Process Payment' command.");
this.currentState = "PAYMENT_PROCESSING";
System.out.println("Saga " + sagaId + " state: " + currentState);
}
public void handlePaymentResponse(boolean success) {
if (success) {
System.out.println("Payment successful. Sending 'Update Inventory' command.");
this.currentState = "INVENTORY_UPDATING";
} else {
System.out.println("Payment failed. Initiating compensation.");
this.currentState = "FAILED";
}
System.out.println("Saga " + sagaId + " state: " + currentState);
}
public String getCurrentState() {
return currentState;
}
public static void main(String[] args) {
OrderSagaOrchestrator orchestrator = new OrderSagaOrchestrator("ORD-123");
orchestrator.startOrderSaga();
orchestrator.handlePaymentResponse(true); // Simulate success
// orchestrator.handlePaymentResponse(false); // Try simulating failure
}
}Orchestrator Communication
For reliable communication, orchestrators typically interact with participant services via a message broker (like Apache Kafka or RabbitMQ).
- Orchestrator publishes commands to queues/topics for specific services.
- Participant services publish events (success or failure) back to topics that the orchestrator subscribes to.
This asynchronous messaging ensures loose coupling and resilience.
Implementing Compensation
If a participant service reports a failure, the orchestrator must initiate compensation. This means reversing any successfully completed steps.
For example, if payment succeeded but inventory update failed, the orchestrator would send a 'RefundPayment' command to the Payment Service.
The orchestrator's persisted state is vital here, as it knows exactly which steps need to be undone.
Quick Check
Which of the following are key responsibilities of a Saga Orchestrator?
Recap: Designing Orchestrators
In this lesson, we learned about designing a saga orchestrator. It's a dedicated service that acts as a central coordinator for distributed transactions.
- It initiates steps, tracks state, and coordinates participant services.
- Key to its design are persistent state management and robust communication via message brokers.
- Orchestrators simplify debugging and managing complex business flows, especially with their built-in compensation logic.
Next, we'll explore how to use state machines to build even more robust orchestrators!
Perguntas Frequentes
A aula “Conceção de orquestradores Saga” é grátis?
Sim — o texto completo de “Conceção de orquestradores Saga” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Microservices Communication Patterns (Saga, Circuit Breaker), atualize para CoddyKit PRO. O curso de Microservices Communication Patterns (Saga, Circuit Breaker) inclui 4 aulas no total.
O que vou aprender em “Conceção de orquestradores Saga”?
Aprenda a conceber um serviço orquestrador dedicado, responsável por gerir o estado e as etapas de uma Saga. Você pratica Microservices Communication Patterns (Saga, Circuit Breaker) com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Microservices Communication Patterns (Saga, Circuit Breaker)?
Nenhuma experiência prévia é necessária. Microservices Communication Patterns (Saga, Circuit Breaker) no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.
Quanto tempo leva a aula “Conceção de orquestradores Saga”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Microservices Communication Patterns (Saga, Circuit Breaker)?
Sim. Cada aula de Microservices Communication Patterns (Saga, Circuit Breaker) inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Conceção de orquestradores Saga
- Máquinas de estados para orquestração
- Implementação com um motor de fluxos de trabalho
- Testes de sagas orquestradas