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 Spring Framework and Spring Boot are great technologies, but what if you want to use Atomikos without Spring? Here is how to do it:
What every architect should know before selecting the next big broker / integration platform, cloud DBMS or remoting stack. Or: how microservices can corrupt your data - even with eventual consistency or sagas.
Pod crashed? Transaction logs lost? Read this…
Looking to use Apache Ignite and its JTA/XA support with Atomikos?
What are the pros and cons of tweaking this parameter?
