A local transaction is an ACID transaction confined to the data and resources managed by one service. It provides a transactional boundary for service-local operations. section 9.4
When an operation spans services, each service commits its own local transaction rather than sharing one distributed ACID transaction. A saga coordinates these transactions; because commits may need to be undone, steps can use compensating transactions. section 9.2 section 9.4
Figure 9.2 A saga replaces what would other be a distributed ACID transaction with a sequence of local ACID transactions in each of the participating services.
Shows a saga replacing a distributed ACID transaction with a sequence of local ACID transactions across participating services. section 9.2
A saga does not inherit ACID isolation: concurrent execution can create data anomalies, so consistency requires application-level design. Distributed queries likewise use independent transactions in each participating service. section 9.4 section 12.1.5
