Long-running transactions 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. 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[1], and WS-CAF[2] are examples. These protocols use a coordinator to mediate the successful completion or use of compensation in a long-running transaction.
