Long-running transaction

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Long-running transaction" – news · newspapers · books · scholar · JSTOR (October 2015) (Learn how and when to remove this message)

|

Long-running transactions (also known as the saga interaction pattern[1][2]) are computer database transactions that avoid locks on non-local resources, use compensation to handle failures, potentially aggregate smaller ACID transactions (also referred to as atomic transactions), and typically use a coordinator to complete or abort the transaction. In contrast to rollback in ACID transactions, compensation restores the original state, or an equivalent, and is business-specific. For example, the compensating action for making a hotel reservation is canceling that reservation.

A number of protocols have been specified for long-running transactions using Web services within business processes. OASIS Business Transaction Processing[3] and WS-CAF[4] are examples. These protocols use a coordinator to mediate the successful completion or use of compensation in a long-running transaction.

## See also

[edit]

* Optimistic concurrency control
* Long-lived transaction

## References

[edit]

1. ^ Garcia-Molina, Hector; Salem, Kenneth (7 January 1987). "SAGAS" (PDF). Princeton, NJ: Department of Computer Science Princeton University.
2. ^ Rotem-Gal-Oz, Arnon (September 24, 2012). "5.4 Saga" (PDF). SOA Patterns (1st ed.). Manning Publications. ISBN 978-1933988269.
3. ^ "OASIS Business Transactions TC | OASIS".
4. ^ "OASIS Web Services Composite Application Framework (WS-CAF) TC | OASIS".