Microservices Communication Patterns (Saga, Circuit Breaker) · 课时

设计 Saga 编排器

学习如何设计专用编排器服务，负责管理 Saga 的状态和步骤。

设计 Saga 编排器 是 CoddyKit 上的免费 Microservices Communication Patterns (Saga, Circuit Breaker) 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Microservices Communication Patterns (Saga, Circuit Breaker) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Microservices Communication Patterns (Saga, Circuit Breaker) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

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!

常见问题解答

「设计 Saga 编排器」课时是免费的吗？

是的 — 「设计 Saga 编排器」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Microservices Communication Patterns (Saga, Circuit Breaker) 课程的其余内容，请升级到 CoddyKit PRO。 Microservices Communication Patterns (Saga, Circuit Breaker) 课程共包含 4 节课。

「设计 Saga 编排器」这节课中我会学到什么？

学习如何设计专用编排器服务，负责管理 Saga 的状态和步骤。你通过在浏览器中直接运行的动手代码来练习 Microservices Communication Patterns (Saga, Circuit Breaker)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Microservices Communication Patterns (Saga, Circuit Breaker) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Microservices Communication Patterns (Saga, Circuit Breaker) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「设计 Saga 编排器」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Microservices Communication Patterns (Saga, Circuit Breaker) 课中编写并运行代码吗？

能。每节 Microservices Communication Patterns (Saga, Circuit Breaker) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Microservices Communication Patterns (Saga, Circuit Breaker)