Release 3.8 is now available

May 31st, 2012

We have released 3.8 of Atomikos ExtremeTransactions and TransactionsEssentials software. This release includes a number of new features including:

  • redesigned logging for compatibility with your favorite logging framework
  • performance improvements
  • OSGi class export improvements
  • an OSGi example application

You can download the release from our website.

Important question to the community

March 22nd, 2012

Your input is needed for our release planning:


Online certification training now available

March 12th, 2012

We’ve finally managed to publish our online training via Parleys - feel free to check it out!

From now on, everybody world-wide can purchase our training sessions and follow at them at a self-paced rhythm. Training when you want it, at your fingertips!

Release 3.7.1 available

March 2nd, 2012

We’ve just released the 3.7.1 (bug fix) releases for ExtremeTransactions and TransactionsEssentials - enjoy!

Atomikos scalability

February 9th, 2012

We’ve know it for a while, but this independent blog post confirms the facts: linear scalability.

Email reception problems

February 9th, 2012

Due to a server migration you may experiencing problems with support emails. We are working to resolve the problem.

In the meantime, thanks for your understanding and patience.

DataNucleus integrates Atomikos

January 2nd, 2012

Check out this news post to learn more about DataNucleus and the details of this news item…

Happy 2012!

January 2nd, 2012

Best wishes for the new year to all of you, from all of us!


Inquiry: redesign of init property lookup

December 22nd, 2011

We are asking for community input on the following: over time, our initialization mechanism (property file, system properties, properties supplied programmatically) has been polluted a bit and as a result the lookups are not always intuitive. We would like to improve this and are working on a new design proposed here. Let us know what you think!

Proposed new property lookup procedure when Atomikos starts:

1. default properties are looked up via a property file in the Atomikos jars (should always be found)
2. override with specific custom properties looked up in the file in the classpath (like now)
3. if no found: NO logging to System.err any more (so no need to disable that with system props either)
4. override with specific properties that are set programmatically on the UserTransactionService
5. resolve any placeholder properties (i.e., ant-style expansion of references to other props)
6. this yields the final properties to use for the init procedure

What do you think? Did we miss something important?


Why BRIC countries love Atomikos

September 15th, 2011

BRIC countries have the tremendous opportunity to start out with no legacy, no old-style infrastructure like application servers, no message brokers, no enterprise service bus (ESB) or other nonsense like that - the typical stuff big enterprise vendors will try to trick you into (if they do: just ignore them - you will be better off).

Instead, BRIC countries have the luxury of being able to pick a light-weight model such as JEE without application server to achieve unlimited scalability at virtually no cost, using commodity hardware and software.

With the recent economic crises in both the US and Europe, it is the BRIC countries that are helping out (instead of the other way around). The future will involve a lot more BRIC. And with that, a lot more Atomikos.

Western companies that want to be as agile, productive and competitive as the BRIC countries: what are you waiting for? Call us to get an introduction and migration path for your legacy.