Extended architecture
In the previous sections, we discussed how the status of the data is permanently persisted at the end of an operation.
However, enterprise applications are composed of complex operations that often involve multiple and heterogeneous data sources, such as databases, message brokers, caches, and so on.
An application functionality must be implemented to ensure the logical consistency of the data; this means that the individual operations that compose it, while insisting on different data sources, must still act as a single unit. They must complete everything successfully, or none of them can affect the status of the data.
How can we achieve this behavior?
The answer is the Extended Architecture (XA) specification. It's ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access