LinkedIn·Monday, 17 August 2026·9d ago
Reliable messaging has two sides. Sending reliably means making sure a business update and its outgoing message stay consistent. Receiving…
Atomikos
1,678 followers
Reliable messaging has two sides.
Sending reliably means making sure a business update and its outgoing message stay consistent.
Receiving reliably means making sure processing a message and updating application state stay consistent.
If either side is handled incorrectly, failures can lead to:
- lost messages
- duplicate processing
- partial business updates
Atomikos supports transaction coordination across JDBC and JMS resources, allowing applications to treat related work as one transaction.
That is the basis of two useful patterns:
Exactly-once sender
Database update + message send succeed or roll back together.
Exactly-once receiver
Message consumption + database update succeed or roll back together.
Both patterns are described in the Microservice Transaction Patterns ebook.
💬 1
View on LinkedIn Cross-referenced
Related on the wire
What disappeared when Java moved away from application servers? More than many teams realized. Application servers bundled a lot together:…
A transaction manager does not prevent failures. It determines what should happen when they do. Imagine one business operation needs to do…
Most microservice transaction discussions start with technology. We think there is a better question to ask first: **What happens if this…
Most architecture diagrams show the happy path. But reliability is usually decided somewhere in the middle. Consider a simple workflow: -…
Twenty years ago we thought the hard problem was distributed transactions. Today we think it's something else. Over two decades of working…
We didn't start by trying to replace application servers. We started by asking a different question. Years ago, many enterprise Java…