Glossary · System coordination, integration and orchestration
Distributed transaction
Also known as: global transaction, two-phase commit transaction
German: Verteilte Transaktion
In distributed systems, a distributed transaction is a transaction that updates data in two or more independent systems or databases so that either all updates take effect or none do, typically coordinated by a protocol such as two-phase commit.
- System integration
In one sentence
A distributed transaction updates data in several systems so that either all changes take effect or none do, usually via two-phase commit.
Example
Booking a finished pallet decrements stock in the warehouse database and creates a shipment record in the logistics database in one distributed transaction.
How it applies
- Architecture: Distributed transactions give strong guarantees but couple systems tightly: all participants must be available and support the protocol, and a failed coordinator can leave participants waiting.
- Integration practice: Across heterogeneous systems such as ERP, MES and cloud services, true distributed transactions are rarely available. Designs then use local transactions plus compensation (Compensating transaction) or reliable messaging, and accept temporary inconsistency.
- Documentation: Document which business operations are atomic across systems and which are not. Support teams need to know what intermediate states can occur after a Partial failure and how to repair them.
Distributed transaction vs. compensating transaction
A distributed transaction prevents inconsistent intermediate states from becoming visible. A compensating transaction allows them and repairs them afterwards.