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!
The Spring Framework and Spring Boot are great technologies, but what if you want to use Atomikos without Spring? Here is how to do it: