Long-running transaction
 | This article needs additional citations for verification. (October 2015) (Learn how and when to remove this template 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.
The 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
References
- ↑ Garcia-Molina, Hector; Salem, Kenneth (7 January 1987). "SAGAS". Princeton, NJ: Department of Computer Science Princeton University. ftp://ftp.cs.princeton.edu/reports/1987/070.pdf.
- ↑ Rotem-Gal-Oz, Arnon (September 24, 2012). "5.4 Saga". SOA Patterns (1st ed.). Manning Publications. ISBN 978-1933988269. http://www.rgoarchitects.com/Files/SOAPatterns/Saga.pdf.
- ↑ "OASIS Business Transactions TC | OASIS". http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=business-transaction.
- ↑ "OASIS Web Services Composite Application Framework (WS-CAF) TC | OASIS". http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-caf.
 |  |
