A version file records operations performed on a database record so concurrent updates can be reordered. It is an application-level countermeasure for the missing isolation of multi-database architectures that do not use distributed transactions. section 9.3.2
Use a version file when concurrently executing sagas can produce anomalies such as lost updates, dirty reads, or fuzzy reads. It belongs alongside other saga countermeasures rather than replacing transaction isolation universally. section 9.3.2 section 9.4
Select the concurrency countermeasure according to the anomaly and business risk:
- Use a semantic lock when an application-level flag must signal that a record is being changed. section 9.3.2
- Use commutative updates when operations can safely execute in any order. section 9.4
- Use a pessimistic view to reorder saga steps and minimize business risk, or reread values to detect changes before overwriting. section 9.3.2
