SOA Patterns > Composition Implementation Patterns > Compensating Service Transaction
Compensating Service Transaction (Utschig, Maier, Trops, Normann, Winterberg, Loesgen, Little)
How can composition runtime exceptions be consistently accommodated without requiring services to lock resources?
Whereas uncontrolled runtime exceptions can jeopardize a service composition, wrapping the composition in an atomic transaction can tie up too many resources, thereby negatively affecting performance and scalability.
Compensating routines are introduced, allowing runtime exceptions to be resolved with the opportunity for reduced resource locking and memory consumption.
Compensation logic is pre-defined and implemented as part of the parent composition controller logic or via individual “undo” service capabilities.
Unlike atomic transactions that are governed by specific rules, the use of compensation logic is open-ended and can vary in its actual effectiveness.
Compensating transactions do not require that resources be locked or that the original state be preserved.