Saga 订单履行架构

Architecture

订单履行 Saga 架构图，包含四个顺序步骤：客户验证、库存预留、支付授权和发货创建，以及在失败时反转已完成步骤的补偿链。该模板将端到端订单生命周期建模为 Saga，展示每个服务如何参与事务以及补偿操作如何维护数据一致性。适合设计可靠订单处理管道的电商架构师。

下载 .fz 文件

完整 FlowZap 代码

OrderSaga { # Order Fulfillment Saga
n1: circle label:"Order Received"
n2: rectangle label:"Validate Order"
n3: rectangle label:"Step 1: Verify Customer"
n4: rectangle label:"Step 2: Check Inventory"
n5: rectangle label:"Step 3: Authorize Payment"
n6: rectangle label:"Step 4: Ship Order"
n7: diamond label:"Saga Complete?"
n8: rectangle label:"Finalize Order"
n9: rectangle label:"Trigger Compensation Chain"
n10: circle label:"Order Fulfilled"
n1.handle(right) -> n2.handle(left)
n2.handle(right) -> n3.handle(left) [label="Valid"]
n3.handle(right) -> n4.handle(left) [label="Verified"]
n4.handle(right) -> n5.handle(left) [label="In Stock"]
n5.handle(right) -> n6.handle(left) [label="Authorized"]
n6.handle(right) -> n7.handle(left)
n7.handle(right) -> n8.handle(left) [label="Success"]
n7.handle(bottom) -> n9.handle(top) [label="Failure"]
n8.handle(right) -> n10.handle(left)
n3.handle(bottom) -> Services.n11.handle(top) [label="Verify"]
n4.handle(bottom) -> Services.n12.handle(top) [label="Reserve"]
n5.handle(bottom) -> Services.n13.handle(top) [label="Charge"]
n6.handle(bottom) -> Services.n14.handle(top) [label="Ship"]
}
Services { # Participating Services
n11: rectangle label:"Customer Service"
n12: rectangle label:"Inventory Service"
n13: rectangle label:"Payment Service"
n14: rectangle label:"Shipping Service"
n11.handle(top) -> OrderSaga.n4.handle(bottom) [label="Customer OK"]
n12.handle(top) -> OrderSaga.n5.handle(bottom) [label="Reserved"]
n13.handle(top) -> OrderSaga.n6.handle(bottom) [label="Charged"]
n14.handle(top) -> OrderSaga.n7.handle(bottom) [label="Shipped"]
}
Compensations { # Compensation Actions
n15: rectangle label:"Reverse Payment"
n16: rectangle label:"Release Inventory"
n17: rectangle label:"Notify Customer"
n18: circle label:"Saga Rolled Back"
n15.handle(right) -> n16.handle(left) [label="Refund"]
n16.handle(right) -> n17.handle(left) [label="Unreserve"]
n17.handle(right) -> n18.handle(left) [label="Apology Email"]
n9.handle(bottom) -> Compensations.n15.handle(top) [label="Compensate"]
}

为什么需要这个工作流？

E-commerce order fulfillment spans customer verification, inventory management, payment processing, and shipping—each owned by a different service. A saga ensures the entire fulfillment pipeline either completes successfully or rolls back cleanly, preventing scenarios like charging customers for out-of-stock items.

工作原理

Step 1: The order is validated and the fulfillment saga begins.
Step 2: Step 1: Customer Service verifies the customer account and shipping address.
Step 3: Step 2: Inventory Service checks stock availability and reserves items.
Step 4: Step 3: Payment Service authorizes and captures the payment.
Step 5: Step 4: Shipping Service creates a shipment and generates tracking.
Step 6: On failure at any step, the compensation chain reverses payment, releases inventory, and notifies the customer.

替代方案

Synchronous orchestration with rollback is simpler but creates long-running transactions. Event-driven choreography distributes the logic but is harder to debug. This template shows the orchestrated saga approach for order fulfillment.

Key Facts

Template Name	Saga 订单履行架构
Category	Architecture
Steps	6 workflow steps
Format	FlowZap Code (.fz file)