Sagas lack isolation across their ACID transactions, so concurrent execution can cause lost updates, dirty reads, and fuzzy reads. Countermeasures use application-level design to prevent these anomalies or reduce their business risk. section 9.3 section 9.4
Five useful strategies for saga-based microservices are:
- Semantic lock — use an application-level lock. section 9.4
- Commutative updates — design operations to work in any order. section 9.4
- Pessimistic view — reorder saga steps to minimize business risk. section 9.4
- Reread value — verify data is unchanged before overwriting it, preventing dirty writes. section 9.4
- Version file — record updates so they can be reordered. section 9.4
