3.3. Multiple-Resource Transactions
The next degree of complexity enters when updates span more than one transactionally aware resource. Going back to the checking account example, imagine that the Logging table is in Database A and the rest of the tables are in Database B. Neither database can now guarantee that all of the updates can be done en masse. Database A can guarantee that its updates are done (or not done), but it has no idea what Database B's opinion is on the subject. Database B is equally ignorant about how Database A feels about the situation.
When we have updates spanning two different transactionally aware resources, we have what I call a multiple-resource transaction. There are two types of multiple-resource transactions: tightly ...
Get Software Fortresses: Modeling Enterprise Architectures 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.
