Penjelasan Saga Orkestrasi
Pelajari pendekatan orkestrasi, yaitu layanan khusus mengoordinasikan tahapan transaksi terdistribusi.
Penjelasan Saga Orkestrasi adalah pelajaran Microservices Communication Patterns (Saga, Circuit Breaker) gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Microservices Communication Patterns (Saga, Circuit Breaker), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Microservices Communication Patterns (Saga, Circuit Breaker) mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Introducing Orchestration Sagas
Welcome to the Orchestration Saga! In a distributed system, sometimes a business transaction needs to involve multiple services.
An Orchestration Saga is a pattern where a central service, called an orchestrator, takes charge of guiding the entire transaction.
The Role of the Orchestrator
Think of the orchestrator as a project manager for your distributed transaction. It knows all the steps and coordinates them.
- It sends commands to participant services.
- It waits for responses (events) from those services.
- It decides the next step based on the responses.
How it Works: A Simple Flow
Unlike a Choreography Saga where services react to events from each other, here the orchestrator is in control:
- Orchestrator sends a command to Service A.
- Service A performs its task and sends a completion event back to the orchestrator.
- Orchestrator receives the event and sends a command to Service B.
- This continues until the transaction is complete.
Example: Online Order Process
Let's use an online order as an example. An order might need to:
- Create an order in the Order Service.
- Reserve items in the Inventory Service.
- Process payment in the Payment Service.
- Initiate shipping in the Shipping Service.
An orchestrator would manage this sequence.
Orchestrator's State Management
The orchestrator must keep track of the saga's current state and context. This means it needs to store information like:
- Which steps have completed?
- What data was returned by previous steps?
- What is the current status (e.g.,
PAYMENT_PENDING,INVENTORY_RESERVED)?
This state is crucial for deciding the next action or handling failures.
Commands & Events
The orchestrator communicates using two main types of messages:
- Commands: Sent from the orchestrator to a service, telling it what to do (e.g.,
ReserveInventory). - Events: Sent from a service back to the orchestrator, reporting the outcome (e.g.,
InventoryReserved,PaymentFailed).
This clear distinction helps maintain control.
Handling Failures & Compensation
What if a step fails? The orchestrator is responsible for compensation.
If the Payment Service fails, the orchestrator detects the PaymentFailed event. It then knows to send compensation commands to previous services, such as ReleaseInventory to the Inventory Service and CancelOrder to the Order Service.
Orchestrator Flow Demo
Let's look at a simplified Java example. This isn't a full microservice, but it shows how an orchestrator's logic might flow, reacting to simulated service outcomes.
Notice how it tracks sagaState and triggers compensation if payment fails.
public class OrderSagaOrchestrator {
public static void main(String[] args) {
System.out.println("Saga Orchestrator Started: Order 123");
String sagaState = "ORDER_INITIATED";
System.out.println("Orchestrator: Sending 'CREATE_ORDER' command.");
// Simulate Order Service success
sagaState = "ORDER_CREATED";
System.out.println("Orchestrator: Received 'ORDER_CREATED' event.");
if (sagaState.equals("ORDER_CREATED")) {
System.out.println("Orchestrator: Sending 'RESERVE_INVENTORY' command.");
// Simulate Inventory Service success
sagaState = "INVENTORY_RESERVED";
System.out.println("Orchestrator: Received 'INVENTORY_RESERVED' event.");
}
if (sagaState.equals("INVENTORY_RESERVED")) {
System.out.println("Orchestrator: Sending 'PROCESS_PAYMENT' command.");
// Simulate Payment Service *failure*
System.out.println("Orchestrator: Received 'PAYMENT_FAILED' event.");
sagaState = "PAYMENT_FAILED";
}
if (sagaState.equals("PAYMENT_FAILED")) {
System.out.println("Orchestrator: Initiating compensation!");
System.out.println("Orchestrator: Sending 'CANCEL_ORDER' command.");
System.out.println("Orchestrator: Sending 'RELEASE_INVENTORY' command.");
sagaState = "SAGA_COMPENSATED";
System.out.println("Orchestrator: Saga completed with compensation.");
} else {
System.out.println("Orchestrator: Sending 'CONFIRM_ORDER' command.");
System.out.println("Orchestrator: Sending 'SHIP_ORDER' command.");
sagaState = "SAGA_COMPLETED_SUCCESSFULLY";
System.out.println("Orchestrator: Saga completed successfully.");
}
}
}Advantages of Orchestration
Orchestration Sagas offer clear benefits:
- Centralized Control: Easier to understand the overall flow.
- Simplified Participant Services: Services don't need to know about the entire saga; they just follow orchestrator commands.
- Easier Debugging: The orchestrator's state makes it simpler to trace issues.
- Explicit Compensation: Compensation logic is clearly defined within the orchestrator.
Check Your Understanding
Which of the following statements accurately describe key characteristics of an Orchestration Saga?
Recap: Orchestration Saga
You've learned about the Orchestration Saga pattern!
- It uses a central orchestrator service to manage a distributed transaction.
- The orchestrator sends commands to services and receives events as responses.
- It maintains the saga's state to know where it is in the transaction.
- It explicitly handles compensation by issuing rollback commands if a step fails.
This pattern provides clear control and simplifies participant services.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Penjelasan Saga Orkestrasi” gratis?
Ya — teks lengkap “Penjelasan Saga Orkestrasi” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Microservices Communication Patterns (Saga, Circuit Breaker), upgrade ke CoddyKit PRO. Kursus Microservices Communication Patterns (Saga, Circuit Breaker) mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Penjelasan Saga Orkestrasi”?
Pelajari pendekatan orkestrasi, yaitu layanan khusus mengoordinasikan tahapan transaksi terdistribusi. Kamu berlatih Microservices Communication Patterns (Saga, Circuit Breaker) dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Microservices Communication Patterns (Saga, Circuit Breaker)?
Tidak diperlukan pengalaman sebelumnya. Microservices Communication Patterns (Saga, Circuit Breaker) di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.
Berapa lama pelajaran “Penjelasan Saga Orkestrasi” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Microservices Communication Patterns (Saga, Circuit Breaker) ini?
Ya. Setiap pelajaran Microservices Communication Patterns (Saga, Circuit Breaker) menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Apa Itu Pola Saga?
- Penjelasan Saga Koreografi
- Penjelasan Saga Orkestrasi
- Memilih antara Choreography dan Orchestration