You are here: Blog » Tech tips

Tech tips

Want to learn how you can manage transactions across independent REST services without being tied into a specific technology vendor?

A common and perceived alternative to JTA/XA transactions in messaging is the so-called Idempotent Consumer or Idempotent Receiver pattern.

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!

Exactly-once delivery (processing) in Kafka? It's not as easy as claimed - read this to find out about the pitfalls…

Really easy integration of Hazelcast with Atomikos JTA/XA functionality…

Guaranteed order of updates is claimed to be hard in distributed systems. It's not - if you read this…

JTA/XA reliability without the performance overhead
Distributed transactions without the performance cost

18 Jan 2018 | Guy Pardon | Tech tips, Vision | , , ,

Who said distributed transactions would cost in terms of performance? Now you can go as fast as with plain JDBC!

Contact Us

Atomikos Corporate Headquarters
Hoveniersstraat, 39/1, 2800
Mechelen, Belgium

T +3215613055

Subscribe to our newsletter

Never miss an update

Copyright 2019 Atomikos BVBA
This website is using cookies. More info. That's Fine