RabbitMQ Messaging & Async Systems · Ders

RabbitMQ ile Saga Örüntüsü

RabbitMQ kullanarak uzun süren dağıtık işlemleri yönetmek için Saga örüntüsünü uygulayın. Birden çok mikro hizmetteki karmaşık iş akışlarını güvenilir biçimde düzenleyin.

RabbitMQ ile Saga Örüntüsü, CoddyKit'te ücretsiz bir RabbitMQ Messaging & Async Systems dersidir. Bu, 4 dersinin 2. 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, RabbitMQ Messaging & Async Systems öğrenme yolunun bir parçasıdır ve ilerlemeniz web ve CoddyKit uygulaması arasında senkronize olur. RabbitMQ Messaging & Async Systems kursu toplamda 4 dersten oluşur.

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

Distributed Transactions Unveiled

In microservices, a single business operation often spans multiple services. For example, placing an order might involve an Order Service, Inventory Service, and Payment Service.

A distributed transaction ensures that all these separate operations either succeed together or fail together, maintaining data consistency across your system.

Beyond Two-Phase Commit

Traditional database transactions often use a Two-Phase Commit (2PC) protocol to ensure atomicity. However, 2PC isn't ideal for microservices because:

It creates tight coupling between services.
It can lead to long-held locks, impacting availability.
It's complex to implement and manage across different technologies.

We need a more flexible approach for distributed systems.

Introducing the Saga Pattern

The Saga pattern is a way to manage distributed transactions. Instead of a single atomic transaction, a saga is a sequence of local transactions, each updating its own service's database.

Each local transaction publishes an event upon completion.
These events trigger the next step in the saga.
If a step fails, compensating transactions are used to undo previous successful steps.

The goal is eventual consistency.

Two Saga Flavors

There are two main ways to implement a Saga:

Orchestration: A central "Saga Orchestrator" service manages and directs the workflow, telling each participant what to do next.
Choreography: Each service produces and listens to events, deciding its own next action without a central coordinator.

For this lesson, we'll focus on the Orchestration approach, which often pairs well with message brokers like RabbitMQ.

The Brain of the Saga

The Saga Orchestrator is a dedicated service responsible for:

Receiving the initial command (e.g., "Create Order").
Sending commands to saga participants (microservices).
Listening for events from participants.
Maintaining the saga's state.
Deciding the next step or initiating compensating transactions if a step fails.

RabbitMQ is perfect for the orchestrator to send commands and receive events.

Participants & Local Transactions

A Saga Participant is a microservice involved in the distributed transaction. When it receives a command from the orchestrator, it:

Performs its own local ACID transaction.
Updates its database.
Publishes an event (e.g., "OrderCreatedEvent", "StockReservedEvent") indicating success or failure.

These events are crucial for the orchestrator to continue the saga.

Undo Actions: Compensation

What happens if a step in the saga fails? This is where compensating transactions come in. They are operations designed to reverse the effects of previously completed local transactions.

For example, if a "Process Payment" step fails, a compensating transaction for "Reserve Stock" might be to release the reserved items back into inventory.

This ensures the system returns to a consistent state, even if not fully rolled back.

Orchestrator Kicks Off

Let's imagine an order creation saga. The orchestrator receives a request and sends a command to the first participant (e.g., "Order Service"). Here's a simplified Java example:

public class OrderSagaOrchestrator {
  public void startOrderCreationSaga(String orderId, String userId, double amount) {
    System.out.println("Orchestrator: Starting saga for Order " + orderId);
    // Simulate sending a message to Order Service
    String command = "CreateOrderCommand { orderId: " + orderId + ", userId: " + userId + ", amount: " + amount + " }";
    System.out.println("Orchestrator: Sending command to Order Service: " + command);
    // In a real app, this would be a RabbitMQ message send
  }

  public static void main(String[] args) {
    OrderSagaOrchestrator orchestrator = new OrderSagaOrchestrator();
    orchestrator.startOrderCreationSaga("ORD-001", "user123", 99.99);
  }
}

Participant Responds

Now, let's look at the "Order Service" (a participant) receiving the command. It processes the order locally and then publishes an event.

public class OrderServiceParticipant {
  public void handleCreateOrderCommand(String commandMessage) {
    System.out.println("OrderService: Received command: " + commandMessage);
    // Simulate local transaction (e.g., save order to DB)
    String orderId = "ORD-001"; // Extract from commandMessage in real app
    System.out.println("OrderService: Successfully created local order " + orderId);

    // Simulate publishing an event back to the orchestrator
    String event = "OrderCreatedEvent { orderId: " + orderId + ", status: 'PENDING_PAYMENT' }";
    System.out.println("OrderService: Publishing event: " + event);
    // In a real app, this would be a RabbitMQ message publish
  }

  public static void main(String[] args) {
    OrderServiceParticipant participant = new OrderServiceParticipant();
    participant.handleCreateOrderCommand("CreateOrderCommand { orderId: ORD-001, userId: user123, amount: 99.99 }");
  }
}

Orchestrator Continues Flow

The orchestrator listens for events like OrderCreatedEvent. Upon receiving it, it updates the saga's state and sends the next command, perhaps to an "Inventory Service" to reserve stock.

public class OrderSagaOrchestratorContinued {
  public void handleOrderCreatedEvent(String eventMessage) {
    System.out.println("Orchestrator: Received event: " + eventMessage);
    String orderId = "ORD-001"; // Extract from eventMessage
    // Update saga state (e.g., mark order as 'OrderCreated')

    // Decide next step: send command to Inventory Service
    String command = "ReserveStockCommand { orderId: " + orderId + ", productId: 'PROD-A', quantity: 2 }";
    System.out.println("Orchestrator: Sending command to Inventory Service: " + command);
  }

  public static void main(String[] args) {
    OrderSagaOrchestratorContinued orchestrator = new OrderSagaOrchestratorContinued();
    orchestrator.handleOrderCreatedEvent("OrderCreatedEvent { orderId: ORD-001, status: 'PENDING_PAYMENT' }");
  }
}

Saga Essentials Check

Which of the following are key components or characteristics of the Saga Orchestration pattern?

Saga for Reliability

The Saga pattern is a powerful way to manage complex, long-running distributed transactions in microservice architectures.

It enables eventual consistency without tight coupling.
It uses local transactions and compensating transactions for resilience.
RabbitMQ provides the perfect backbone for the orchestrator and participants to communicate reliably through commands and events.

While adding complexity, Sagas are essential for building robust distributed systems.

Sıkça Sorulan Sorular

“RabbitMQ ile Saga Örüntüsü” dersi ücretsiz mi?

Evet — “RabbitMQ ile Saga Örüntüsü” 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 RabbitMQ Messaging & Async Systems kursunun geri kalanını açmak için CoddyKit PRO'ya yükselt. RabbitMQ Messaging & Async Systems kursu toplamda 4 dersten oluşur.

“RabbitMQ ile Saga Örüntüsü” dersinde ne öğreneceğim?

RabbitMQ kullanarak uzun süren dağıtık işlemleri yönetmek için Saga örüntüsünü uygulayın. Birden çok mikro hizmetteki karmaşık iş akışlarını güvenilir biçimde düzenleyin. RabbitMQ Messaging & Async Systems 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.

RabbitMQ Messaging & Async Systems öğrenmeye başlamak için deneyim gerekli mi?

Önceden deneyim gerekmez. CoddyKit'te RabbitMQ Messaging & Async Systems, 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 2. dersidir.

“RabbitMQ ile Saga Örüntüsü” 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 RabbitMQ Messaging & Async Systems dersinde kod yazıp çalıştırabilir miyim?

Evet. Her RabbitMQ Messaging & Async Systems 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

Mesaj İşlemede İdempotentlik
RabbitMQ ile Saga Örüntüsü
Komut-Sorgu Sorumluluklarının Ayrılması (CQRS)
Güvenilir Yayınlama için Outbox Deseni

← RabbitMQ Messaging & Async Systems Sayfasına Dön