分布式事务的 Saga 模式
使用带补偿操作的 Saga 模式，在没有全局事务的情况下协调多个微服务之间的数据一致性。
分布式事务的 Saga 模式 是 CoddyKit 上的免费 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 AI Powered SaaS: Stripe + Auth + Billing + Deploy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Why Distributed Transactions Are Hard
In a monolith one database transaction can update everything atomically. With microservices each service owns its own database, so a single ACID transaction across them is not possible.
Introducing Sagas
A saga is a sequence of local transactions, one per service. Each step publishes an event that triggers the next. If a step fails, earlier steps are undone with compensating actions.
A Concrete Example
An order saga might be: reserve inventory, charge payment, schedule shipping. Each is a local transaction in its own service, linked together as one logical workflow.
Compensating Transactions
There is no rollback across services, so you compensate. If payment fails after inventory was reserved, you run a compensating action to release the inventory.
Choreography Style
In choreography, services react to each other events with no central coordinator. The inventory service emits InventoryReserved; the payment service listens and reacts.
Choreography Trade-offs
Choreography is decoupled and simple for short flows, but the overall workflow is implicit and hard to follow as steps grow. Debugging means tracing events across many services.
Orchestration Style
In orchestration, a central orchestrator tells each service what to do and tracks progress. The workflow lives in one place, making it easier to reason about.
orchestrator:
step1 -> reserveInventory
step2 -> chargePayment
onFailure -> releaseInventoryIdempotency Is Essential
Events may be delivered more than once. Every step and compensation must be idempotent so retries do not double-charge or double-reserve. Use a unique operation id to dedupe.
Tracking Saga State
The orchestrator persists the current step so it can resume after a crash. Store saga state durably and mark each step as pending, completed, or compensated.
Handling Partial Failures
If a compensation itself fails, retry it with backoff and alert operators. Sagas guarantee eventual consistency, not instant consistency, so design the UI to reflect in-progress states.
When to Use Sagas
Use sagas when a business process spans multiple services and must remain consistent. For a single service, a normal database transaction is simpler and preferred. Do not add saga complexity unless you actually cross service boundaries.
Quick Check
Check your saga knowledge.
Recap
You learned the saga pattern for cross-service consistency:
- Break a transaction into local steps with compensating actions
- Coordinate via choreography (events) or orchestration (central coordinator)
- Make steps idempotent and persist saga state
- Accept eventual consistency
Sagas keep distributed workflows reliable without a global transaction.
用 AI 导师学习 AI Powered SaaS: Stripe + Auth + Billing + Deploy — 免费
在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。
- 课程
- 12
- 课程
- 48
常见问题解答
「分布式事务的 Saga 模式」课时是免费的吗？
是的 — 「分布式事务的 Saga 模式」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课程的其余内容，请升级到 CoddyKit PRO。 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课程共包含 4 节课。
「分布式事务的 Saga 模式」这节课中我会学到什么？
使用带补偿操作的 Saga 模式，在没有全局事务的情况下协调多个微服务之间的数据一致性。 你通过在浏览器中直接运行的动手代码来练习 AI Powered SaaS: Stripe + Auth + Billing + Deploy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 AI Powered SaaS: Stripe + Auth + Billing + Deploy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「分布式事务的 Saga 模式」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课中编写并运行代码吗？
能。每节 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。