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!
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.
In this article we'll be debunking 4 microservice myths that can get you into trouble, and point you towards 5 common pitfalls that will ruin your data consistency in the long run…
What can you do if a deployment goes wrong in your microservices environment?
How do you process JMS messages with higher performance? With XA!
