Microservices Communication Patterns (Saga, Circuit Breaker) · درس

شرح Saga بالتنسيق اللامركزي

افهموا نهج التنسيق اللامركزي، حيث تتواصل الخدمات مباشرةً عبر الأحداث دون منسّق مركزي.

شرح Saga بالتنسيق اللامركزي درس مجاني في Microservices Communication Patterns (Saga, Circuit Breaker) على CoddyKit. هذا هو الدرس 2 من أصل 4. يمكنك قراءة الدرس كاملاً أدناه مجاناً — ثم تمرن عليه مباشرة في المتصفح باستخدام محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7. هذا الدرس جزء من مسار التعلم في Microservices Communication Patterns (Saga, Circuit Breaker)، وتقدمك يتزامن عبر الويب وتطبيق CoddyKit. تتضمن دورة Microservices Communication Patterns (Saga, Circuit Breaker) 4 دروس في المجموع.

بعض أجزاء هذا الدرس لم تُترجم بعد وتظهر باللغة الإنجليزية.

Choreography Saga Intro

Welcome! In this lesson, we'll explore the Choreography Saga pattern. It's a way to manage complex business transactions that span multiple services in a decentralized way.

Unlike an orchestra with a conductor, choreography is like a dance where each dancer knows their part and reacts to others' movements.

Decentralized Event Flow

In a choreography saga, there's no central coordinator service. Instead, each service involved in the transaction publishes events and listens for events from other services.

Services react to events.
They perform their part of the transaction.
They publish new events to trigger the next step.

Order Processing Example

Let's use a common example: processing a customer order. This involves multiple steps across different services:

Order Service: Creates the order.
Payment Service: Handles payment.
Inventory Service: Updates stock.

How do these services coordinate without a central brain?

Step 1: Order Created Event

When a customer places an order, the Order Service starts the saga. It saves the order and then publishes an OrderCreatedEvent.

This event signals to other services that a new order is ready for processing.

public class OrderService {
  public static void processNewOrder(String orderId) {
    System.out.println("Order Service: Received new order " + orderId);
    System.out.println("Order Service: Saving order " + orderId + " to database...");
    // Imagine database interaction here
    System.out.println("Order Service: Order " + orderId + " saved.");
    System.out.println("Order Service: Publishing 'OrderCreatedEvent' for " + orderId);
  }

  public static void main(String[] args) {
    processNewOrder("ORD789"); // Simulate a new order coming in
  }
}

Step 2: Payment Service Reacts

The Payment Service is subscribed to OrderCreatedEvents. When it receives one, it processes the payment for that order.

After processing, it publishes either a PaymentProcessedEvent or a PaymentFailedEvent.

public class PaymentService {
  public static void handleOrderCreated(String orderId) {
    System.out.println("Payment Service: Received 'OrderCreatedEvent' for order " + orderId);
    System.out.println("Payment Service: Processing payment for " + orderId + "...");
    // Simulate payment gateway interaction
    boolean paymentSuccess = true; // For this example, assume success
    if (paymentSuccess) {
      System.out.println("Payment Service: Payment successful for " + orderId + ".");
      System.out.println("Payment Service: Publishing 'PaymentProcessedEvent' for " + orderId);
    } else {
      System.out.println("Payment Service: Payment failed for " + orderId + ".");
      System.out.println("Payment Service: Publishing 'PaymentFailedEvent' for " + orderId);
    }
  }

  public static void main(String[] args) {
    handleOrderCreated("ORD789"); // Simulate receiving an event
  }
}

Step 3: Inventory Service Updates

Next, the Inventory Service listens for PaymentProcessedEvents. Upon receiving one, it reduces the stock for the ordered items.

It then publishes an InventoryUpdatedEvent to indicate its task is complete.

public class InventoryService {
  public static void handlePaymentProcessed(String orderId) {
    System.out.println("Inventory Service: Received 'PaymentProcessedEvent' for order " + orderId);
    System.out.println("Inventory Service: Updating stock for order " + orderId + "...");
    // Simulate inventory database update
    System.out.println("Inventory Service: Stock updated for order " + orderId + ".");
    System.out.println("Inventory Service: Publishing 'InventoryUpdatedEvent' for " + orderId);
  }

  public static void main(String[] args) {
    handlePaymentProcessed("ORD789"); // Simulate receiving an event
  }
}

The Challenge of Failures

What happens if a step in this flow fails? For example, if the payment fails, we can't update inventory. We also need to undo any previous successful steps.

This is where compensation logic comes in. It's about reversing previously completed actions.

Compensation in Choreography

In a choreography saga, compensation also happens through events. If a service fails, it publishes a compensation event.

Other services listen for these compensation events and perform their own rollback actions.

Compensation Example: Payment Fails

Imagine the Payment Service fails and publishes a PaymentFailedEvent. The Order Service, which started the saga, listens for this event.

Upon receiving it, the Order Service updates the order status to 'Cancelled', effectively rolling back the transaction from its side.

public class OrderService {
  public static void handlePaymentFailed(String orderId) {
    System.out.println("Order Service: Received 'PaymentFailedEvent' for order " + orderId);
    System.out.println("Order Service: Initiating compensation for " + orderId + ".");
    // Change order status to 'Cancelled'
    System.out.println("Order Service: Updating order " + orderId + " status to 'Cancelled'.");
    // Could publish OrderCancelledEvent if other services need to know
  }

  public static void main(String[] args) {
    handlePaymentFailed("ORD789"); // Simulate receiving a compensation event
  }
}

Pros and Cons of Choreography

Choreography offers benefits but also presents challenges:

Pros: Highly decoupled services, no central point of failure, simpler to implement for simple flows.
Cons: Can be harder to monitor the overall transaction flow, complex compensation logic, potential for 'event storms' if not designed carefully.

Choreography Check

Consider a choreography saga where an 'OrderConfirmedEvent' is published. Which statement accurately describes how the next step is initiated?

Recap: Choreography Saga

You've learned about the Choreography Saga pattern:

It's a decentralized approach for distributed transactions.
Services communicate by publishing and subscribing to events.
There's no central coordinator; each service knows its role.
Compensation for failures is also handled via events, allowing services to roll back their actions.

This pattern promotes loose coupling but requires careful design for monitoring and compensation.

الأسئلة الشائعة

هل درس «شرح Saga بالتنسيق اللامركزي» مجاني؟

نعم — نص درس «شرح Saga بالتنسيق اللامركزي» كامل متاح مجاناً هنا على الويب. لتمرينه بشكل تفاعلي (محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7) وفتح باقي دورة Microservices Communication Patterns (Saga, Circuit Breaker)، انتقل إلى CoddyKit PRO. تتضمن دورة Microservices Communication Patterns (Saga, Circuit Breaker) 4 دروس في المجموع.

ماذا ستتعلم في «شرح Saga بالتنسيق اللامركزي»؟

افهموا نهج التنسيق اللامركزي، حيث تتواصل الخدمات مباشرةً عبر الأحداث دون منسّق مركزي. تتمرن على Microservices Communication Patterns (Saga, Circuit Breaker) مع أكواد عملية تشغلها مباشرة في المتصفح، ومدرس ذكاء اصطناعي متاح 24/7 يجيب على أسئلتك أثناء عملك.

هل أحتاج إلى خبرة سابقة لأبدأ Microservices Communication Patterns (Saga, Circuit Breaker)؟

لا تُشترط خبرة سابقة. Microservices Communication Patterns (Saga, Circuit Breaker) على CoddyKit منظم للمبتدئين حتى المتقدمين، لذا يمكنك البدء من هنا أو من البداية والتقدم بسرعتك الخاصة. هذا هو الدرس 2 من أصل 4.

كم من الوقت يستغرق درس «شرح Saga بالتنسيق اللامركزي»؟

معظم دروس CoddyKit تستغرق حوالي 5–10 دقائق. كل منها موجز وتفاعلي، لذا تحرز تقدماً مستمراً وتستأنف من حيث توقفت عبر الويب والتطبيق.

هل يمكنني كتابة وتشغيل أكواد في درس Microservices Communication Patterns (Saga, Circuit Breaker) هذا؟

نعم. كل درس في Microservices Communication Patterns (Saga, Circuit Breaker) يتضمن محرر أكواد مدمج، لذا تكتب وتشغل أكواداً حقيقية مباشرة في متصفحك وتحصل على تعليقات فورية من الذكاء الاصطناعي — بدون إعداد محلي.

جميع الدروس في هذه الدورة

← العودة إلى Microservices Communication Patterns (Saga, Circuit Breaker)