Long running transaction

Long-running transactions (also known as the saga interaction pattern[1]) 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, possibly with a penalty.

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

References

  1. ^Rotem-Gal-Oz, Arnon (September 24, 2012). “5.4 Saga” (PDF). SOA Patterns (1st ed.). Manning Publications. ISBN 1933988266.
  2. ^http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=business-transaction
  3. ^http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-caf

Ofer Abarbanel – Executive Profile

Ofer Abarbanel online library

Ofer Abarbanel online library

Ofer Abarbanel online library

Ofer Abarbanel online library