ACD is a transaction model providing atomicity, consistency, and durability without isolation. In saga-based systems, this absence of isolation can produce anomalies that developers must prevent or minimize. section 9.3.2
Mitigates isolation anomalies through application-level countermeasures:
- Semantic locks mark records as pending or uncommitted. section 9.3.2
- Commutative updates remain safe when executed in different orders. section 9.3.2
- Pessimistic views reorder saga steps to minimize business risk. section 9.3.2
- Rereading values verifies that data is unchanged before overwriting it. section 9.3.2
- Version files record updates so they can be reordered. section 9.3.2
- Business risk can dynamically select the concurrency mechanism. section 9.3.2
Pending order state
A Create Order Saga begins by setting an Order to a state such as APPROVAL_PENDING, signaling that another transaction is updating it and should act accordingly. section 9.3.2
