Companies embracing service oriented architectures are characterized by many complex internal business processes, and growth in the number of composite applications. For instance, the seemingly simple reservation of a phone number for a subscriber/customer within a telecommunications firm involves a series of automated steps connected to a larger business process.
Architects in SOA environments have typically turned to business process execution language (BPEL) for web services to describe a business process. But BPEL also requires that for every prescribed step in the process, one must also model the reverse path in the event of error. This method of programatically defining business processes is unwieldy, unreliable and quite brittle.
offers a patent-pending Try-Confirm/Cancel (TCC) approach for managing two-phase compensation-based transactions.
Regardless of the complexity of the transaction tree, or the business process, Atomikos ExtremeTransactions®
maintains a total awareness of the transaction and broad system involvement, automating recovery in the event of error or transaction failure.
Any error paths are taken out of the workflow and entirely handled by Atomikos.
Besides TCC, Atomikos ExtremeTransactions®
also supports plain, ACID-style transactions across different web services.