Chapter 10. Using transactions with Mule
In this chapter
- Introducing transactional concepts
- Using single resource transactions
- Using XA transactions with multiple resources
A transaction, whether occurring in software or in real life, is a series of events that need to occur in a specified sequence, leaving all participants in some predetermined state. Leaving the software world aside for a moment, let’s consider a real-world example: paying for groceries in a supermarket. In such a transaction, the following steps need to occur in the specified order:
1.
You place your groceries on the counter.
2.
The cashier scans each item, adding the price of the item to the register.
3.
The cashier sums the prices of the items and communicates ...
Get Mule in Action now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
