Common Use Cases

Typical use cases of ExtremeTransactions are the following:

  • Receiving a message from a JMS queue/topic and updating a database accordingly. In this case, ExtremeTransactions guarantees the following: if there is a crash then either the message remains on the queue or its results have been successfully inserted in the database. In other words: you never lose in-flight transactions.

  • Updating a database and posting a message to a JMS queue/topic in one go. If you use ExtremeTransactions then you have the guarantee that either both happen, or none.

  • Updating two different databases in one go. With ExtremeTransactions you have the guarantee that updates are applied everywhere, or nowhere at all.

  • Transactions spanning multiple (web) services: when a failure happens, our software wipes out the effects everywhere, even across the globe if needed.
Go
r3 - 01 Mar 2008 - 10:46:00 - MichaelDaum
This site is powered by the TWiki collaboration platformCopyright © contributing authors and Atomikos. All material on this collaboration platform is the shared property of the contributing authors and Atomikos.
Syndicate this site RSSATOM