Microservices Communication Patterns (Saga, Circuit Breaker) · Ders

Saga Orkestratörleri Tasarlama

Bir saganın durumunu ve adımlarını yönetmekten sorumlu özel bir orkestratör hizmeti tasarlamayı öğrenin.

Saga Orkestratörleri Tasarlama, CoddyKit'te ücretsiz bir Microservices Communication Patterns (Saga, Circuit Breaker) dersidir. Bu, 4 dersinin 1. dersidir. Aşağıdan dersin tamamını ücretsiz okuyabilir, sonra tarayıcıda yerleşik kod editörü ve 7/24 yapay zeka koçu ile uygulamalı olarak pratik yapabilirsin. Bu, Microservices Communication Patterns (Saga, Circuit Breaker) öğrenme yolunun bir parçasıdır ve ilerlemeniz web ve CoddyKit uygulaması arasında senkronize olur. Microservices Communication Patterns (Saga, Circuit Breaker) kursu toplamda 4 dersten oluşur.

Bu dersin bazı bölümleri henüz çevrilmemiş olup İngilizce olarak gösterilmektedir.

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!

Sıkça Sorulan Sorular

“Saga Orkestratörleri Tasarlama” dersi ücretsiz mi?

Evet — “Saga Orkestratörleri Tasarlama” dersin tüm metni burada web'de ücretsiz olarak okunabilir. Etkileşimli olarak pratik yapmak (yerleşik kod editörü ve 7/24 yapay zeka koçu) ve Microservices Communication Patterns (Saga, Circuit Breaker) kursunun geri kalanını açmak için CoddyKit PRO'ya yükselt. Microservices Communication Patterns (Saga, Circuit Breaker) kursu toplamda 4 dersten oluşur.

“Saga Orkestratörleri Tasarlama” dersinde ne öğreneceğim?

Bir saganın durumunu ve adımlarını yönetmekten sorumlu özel bir orkestratör hizmeti tasarlamayı öğrenin. Microservices Communication Patterns (Saga, Circuit Breaker) ile uygulamalı kodu tarayıcıda doğrudan çalıştırarak pratik yaparsın ve 7/24 yapay zeka koçu dersi çalışırken sorularını yanıtlar.

Microservices Communication Patterns (Saga, Circuit Breaker) öğrenmeye başlamak için deneyim gerekli mi?

Önceden deneyim gerekmez. CoddyKit'te Microservices Communication Patterns (Saga, Circuit Breaker), başlangıçtan ileri seviyeye kadar yapılandırıldığı için buradan başlayabilir veya başından başlayıp kendi hızında ilerleme yapabilirsin. Bu, 4 dersinin 1. dersidir.

“Saga Orkestratörleri Tasarlama” dersi ne kadar sürer?

Çoğu CoddyKit dersi yaklaşık 5–10 dakika sürer. Her biri kısa ve etkileşimli olduğu için sabit ilerleme yaparsın ve web ile uygulama arasında tam olarak bıraktığın yerden devam edebilirsin.

Bu Microservices Communication Patterns (Saga, Circuit Breaker) dersinde kod yazıp çalıştırabilir miyim?

Evet. Her Microservices Communication Patterns (Saga, Circuit Breaker) dersi yerleşik bir kod editörü içerir, bu sayede tarayıcıda gerçek kod yazıp çalıştırabilir ve anlık yapay zeka geri bildirimi alırsın — yerel kurulum gerekli değildir.

Bu kursun tüm dersleri

← Microservices Communication Patterns (Saga, Circuit Breaker) Sayfasına Dön