A serialization anomaly occurs when concurrent sagas interleave and produce an outcome that no serial execution could produce. Because sagas lack isolation across services, correct local transactions do not guarantee that the combined result preserves business invariants. section 9.3.1
Common forms include:
- Lost updates: one saga overwrites another’s change without detecting the conflict. section 9.3.1
- Dirty reads, nonrepeatable reads, and phantom reads: saga steps observe uncommitted data or changing values and query results. section 9.3.1
- Write skew: concurrent sagas update disjoint data after reading overlapping data, violating a business invariant. section 9.3.1
Figure 9.7 Concurrent execution of these two sagas leaves the system in an inconsistent state. The Create Order Saga overwrites the change to the Order state. The Cancel Order Saga releases credit that was never reserved.
The concurrent create-order and cancel-order sagas illustrate an overwritten order state and credit released even though it was never reserved. section 9.3.1

