Pola Saga untuk Transaksi Terdistribusi
Pelajari cara menjaga konsistensi data di seluruh layanan mikro tanpa transaksi terdistribusi menggunakan pola Saga dengan orkestrasi dan koreografi.
Pola Saga untuk Transaksi Terdistribusi adalah pelajaran System Design Basics for Backend Developers gratis di CoddyKit. Ini adalah pelajaran 4 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 System Design Basics for Backend Developers, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus System Design Basics for Backend Developers mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
The Distributed Transaction Problem
In a monolith, one database transaction can update everything atomically. In microservices, each service owns its own database, so a single classic transaction across them is impractical.
How do you keep data consistent when an operation spans multiple services?
Why Not Two-Phase Commit?
Two-phase commit (2PC) can coordinate a distributed transaction, but it locks resources across services and blocks if the coordinator fails. It scales poorly and hurts availability — usually the wrong fit for microservices.
Enter the Saga
A Saga breaks a business transaction into a sequence of local transactions, one per service. Each step publishes an event or sends a command to trigger the next.
There is no global lock — consistency is achieved over time.
Compensating Transactions
If a later step fails, the saga cannot roll back like a database. Instead it runs compensating transactions that semantically undo the earlier steps.
- Order placed -> compensate by cancelling order
- Payment charged -> compensate by refunding
An Order Saga
Consider placing an order: reserve inventory, charge payment, schedule shipping. If payment fails, you compensate by releasing the inventory.
steps = ['reserve_inventory', 'charge_payment', 'schedule_shipping']
compensations = ['release_inventory', 'refund_payment', 'cancel_shipping']
done = []
for i, step in enumerate(steps):
ok = step != 'charge_payment'
if not ok:
print('FAILED at', step)
for j in reversed(range(len(done))):
print('compensate:', compensations[j])
break
done.append(step)
print('ok:', step)Choreography
In choreography, there is no central coordinator. Each service listens for events and reacts by doing its work and emitting the next event. It is decentralized and loosely coupled.
OrderCreated -> (Inventory) -> InventoryReserved
InventoryReserved -> (Payment) -> PaymentCharged
PaymentCharged -> (Shipping) -> OrderShippedChoreography Trade-offs
Choreography is simple for short flows but the overall logic is scattered across services. With many steps it becomes hard to understand and risks cyclic event dependencies.
Orchestration
In orchestration, a central orchestrator tells each service what to do and tracks progress. The workflow lives in one place, making complex sagas easier to reason about and monitor.
Orchestrator:
-> Inventory.reserve()
-> Payment.charge()
-> Shipping.schedule()
on failure -> run compensations in reverseIdempotency Is Mandatory
Messages can be delivered more than once, so every saga step and compensation must be idempotent. Use an idempotency key so re-processing the same message has no extra effect.
Eventual Consistency
Sagas give eventual consistency, not immediate. There is a window where the system is partially updated. Design the UI and business rules to tolerate this — for example, an order shown as PENDING until confirmed.
Choosing an Approach
Use choreography for simple flows with few participants, and orchestration when the workflow is complex or needs central visibility. Either way, make steps idempotent and define a compensation for every action.
Quick Check
Test your understanding of the Saga pattern.
Recap
You learned how microservices stay consistent without distributed transactions:
- Sagas chain local transactions with compensations for failures
- Choreography is decentralized; orchestration is centralized
- Steps must be idempotent against duplicate delivery
- The result is eventual consistency, which the design must tolerate
Belajar System Design Basics for Backend Developers dengan tutor AI — gratis
Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.
- Kursus
- 12
- Pelajaran
- 48
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pola Saga untuk Transaksi Terdistribusi” gratis?
Ya — teks lengkap “Pola Saga untuk Transaksi Terdistribusi” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus System Design Basics for Backend Developers, upgrade ke CoddyKit PRO. Kursus System Design Basics for Backend Developers mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Pola Saga untuk Transaksi Terdistribusi”?
Pelajari cara menjaga konsistensi data di seluruh layanan mikro tanpa transaksi terdistribusi menggunakan pola Saga dengan orkestrasi dan koreografi. Kamu berlatih System Design Basics for Backend Developers 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 System Design Basics for Backend Developers?
Tidak diperlukan pengalaman sebelumnya. System Design Basics for Backend Developers 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 4 dari 4.
Berapa lama pelajaran “Pola Saga untuk Transaksi Terdistribusi” 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 System Design Basics for Backend Developers ini?
Ya. Setiap pelajaran System Design Basics for Backend Developers 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
- Dekomposisi Monolit
- Penemuan dan Registri Layanan
- Pola Komunikasi Antar-Layanan
- Pola Saga untuk Transaksi Terdistribusi