By jpurdy on May 31, 2012
While the costs of XA transactions are well known (e.g. increased data contention, higher latency, significant disk I/O for logging, availability challenges, etc.), in many cases they are the most attractive option for coordinating logical transactions across multiple resources.
There are a few common approaches when integrating Coherence into applications via the use of an application server's transaction manager:
- Use of Coherence as a read-only cache, applying transactions to the underlying database (or any system of record) instead of the cache.
- Use of TransactionMap interface via the included resource adapter.
- Use of the new ACID transaction framework, introduced in Coherence 3.6.
Each of these may have significant drawbacks for certain workloads.