Want to learn how you can manage transactions across independent REST services without being tied into a specific technology vendor?
This tech tip takes a closer look at what 'reliable' messaging means and how to achieve it. As we will see, it all depends on how you configure and use your JMS.
This tech tip explores some patterns for distributed transactions.
Transactions without app server - with power features and support!
Stop gambling with your data integrity.
From debunking the "XA is slow" myth to solving cloud-native recovery with LogCloud, we are showing you how to reclaim your developer productivity and bring 100% atomicity to your microservices.
How do I manage distributed transactions?
Synchronous microservices look great on paper.
They are easy to read, easy to debug, and they map perfectly to how we think: “I send a request, I get a reply.” No surprises, right?
Except when things go wrong. Which in distributed systems is most of the time.
The bad guys are trying to get into your projects. What can you do to avoid pulling in bad code?
We were informed about a potential security issue with Log4J:
Watch the explanation in this YouTube videoPlease adjust your Log4J dependency versions accordingly, to avoid any risk. No new Atomikos release needs to be installed since this is isolated to a 3rd party library dependency marked as optional, so it is not pulled in transitively. The API has been stable so it works with the latest secure Log4J versions at the time of publishing.