Microservices Communication Patterns (Saga, Circuit Breaker) · レッスン

Sagaオーケストレーターの設計

Sagaの状態と各ステップを管理する専用オーケストレーターサービスの設計方法を学習します。

「Sagaオーケストレーターの設計」はCoddyKit上の無料Microservices Communication Patterns (Saga, Circuit Breaker)レッスンです。これはレッスン1/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応の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オーケストレーターの設計」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Microservices Communication Patterns (Saga, Circuit Breaker)コースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Microservices Communication Patterns (Saga, Circuit Breaker)コースには全4レッスンが含まれています。

「Sagaオーケストレーターの設計」で何を学びますか？

Sagaの状態と各ステップを管理する専用オーケストレーターサービスの設計方法を学習します。ブラウザで直接実行するハンズオンコードでMicroservices Communication Patterns (Saga, Circuit Breaker)を演習し、24時間対応の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)に戻る