Data inconsistency occurs when related data does not agree across services or components. In a fine-grained architecture, complex requests spanning services can produce subtle inconsistencies that are difficult to diagnose. Requests updating data in multiple services must use the Saga pattern to maintain consistency. section 2.2.4
Examples of inconsistencies include:
- An order is not delivered because the application fails to assign a courier. section 2.2.4
- A customer cancels an order immediately after placing it, but the application fails to issue a refund. section 2.2.4
Excessively complex sagas can obscure bugs, while interactions between services make diagnosis and repair difficult. section 2.2.4

