Atomikos is designed along the ports and adapters/hexagonal architecture as described here by Alistair Cockburn.

Among other things, this means that it is relatively easy to:

• Implement new transaction APIs / standards / models
• Add new types of two-phase commit resources

Examples of things we've been able to realize thanks to this:

• JTA (port) / XA (adapter)
• TCC (port/adapter)
• RMI (port/adapter)

The port and adapter model is also an important concept in the new book Implementing Domain-Driven Design. Our domain is 2-phase commit. Our adapter is our Participant model. Our ports are all the ways you can interact with our core system.

Transactions are easy to misconfigure, and XA drivers are often buggy in unexpected ways - both of which are problems that are hard to detect by regular testing or code reviews. Our subscribers have access to Development Support and the resulting Application Certification guarantees. It is the only way to make sure that you are not running an unsupported or misconfigured configuration, and also get the necessary Atomikos fixes to go to production on the right foot. This is the only safe way for production systems: unless we can certify your configuration, you might as well not use transactions in the first place.

We are also the only player in the industry that allows customized system configurations, i.e. without forcing you into the harness of a preconfigured application (server) stack that contains lots of technologies that you don't want or need. With Atomikos, you can pick your own and still have peace of mind.

Lastly, Atomikos is also the only safe choice for integration because we are probably the only vendor-independent integration player on the market. Be compatible with the specs we must, and that is your best guarantee to success for all your integration projects.

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

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.

If you have been purchasing the 'Enterprise Architecture' portfolio from the big O then guess what: you've paid way too much for something you don't need, and which will overload your (way too heavy) hardware even more.

We've been claiming this for years so it is about time to show it: how to replace Tuxedo applications with open source and free software. Coming soon to this site!

Stay with us…

PS Tuxedo is a registered trademark owned by Oracle