Sagas execute multiple ACID transactions without transaction isolation. Concurrent sagas can therefore produce lost updates, dirty reads, and fuzzy reads, making application-level countermeasures necessary. section 9.3.2 section 9.4
A commutative update designs an update operation so compatible operations can execute in any order and still produce an equivalent result. It is one countermeasure for missing isolation in sagas and other multi-database architectures. section 9.3.2
Use the technique as part of saga concurrency design:
- Choose it when saga updates can safely be made order-independent, allowing concurrent execution without relying on distributed transactions. section 9.3.2
- Compare it with semantic locks, pessimistic views, rereading values, and version files when selecting an application-level isolation mechanism. section 9.3.2 section 9.4
- Prefer sequential saga steps when simpler reasoning and implementation outweigh the performance benefit of parallel execution. section 9.4
