New maven repository settings for 3.9 and later releases

December 18th, 2013

As of 3.9 on, you can configure our website as a maven repository for transparent access to support releases.

See this page for details on how to do this.

Release 3.9.2 is out

December 18th, 2013

We’ve just published release 3.9.2 with improved OSGi examples, OSGi docs and more. Details are here.


Release 3.9 available

November 15th, 2013

Release 3.9 is available!

The most important new features are JMX controls for JDBC/JMS (reserved for paying subscribers) and support for “domain events” in the core.

Full details are available on the release notes page


Atomikos continues to support OSGi

November 11th, 2013

If you’ve been following the recent cyber-news then you may have heard about more and more vendors abandoning OSGi support.

Just to be clear: we are _not_ part of this club - quite the contrary: Atomikos continues to invest in OSGi compatibility and improved integration with OSGi environments. It’s a major thing for us. Why? Because we design(ed) our products to integrate into your IT ecosystem.

3.9.0.M1 released!

June 8th, 2013

We’ve just released the 3.9.0.M1 - available via the download pages as usual.

Some highlights: redesigned connection pool (much better!), write-ahead logging for double logging performance (subscribers only) and a new distribution model to speed up the build of support / bug fix releases.


Forum account registration troubles - now it should work again

June 8th, 2013

To all candidate community members who did not manage to create a forum account:

now it should work again!

Security settings and anti-spam measures somehow broke the registration process - apologies for that :-(

Atomikos maven repository now open to customers only

December 15th, 2012

We’ve restricted access to (our maven repository) to customers only, so they can have easy and timely access to bug fixes, maintenance releases and full feature releases.

If you’re not a customer then you have two options:

In the near future we plan to distribute TransactionsEssentials exclusively via the central maven repo.

The “ports and adapters” architecture (aka “hexagonal architecture”)

December 15th, 2012

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)
  • WS-AT (port/adapter)
  • CORBA’s OTS (port/adapter)
  • TaaS - Transactions for REST (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.

Looking for early adopters for REST transactions and light-weight BPM

October 3rd, 2012

Early adopters wanted! We are working on something radically different and new in the industry, being a light-weight transaction (and BPM) model for REST with the following characteristics:

  • Guaranteed interoperability
  • Easy and intuitive to use
  • No technology dependencies, so no configuration required
  • Compatible with the REST architectural constraints

To get an idea of what it is like, consider the following example: a telco operator wants to allow customers to acquire ‘personalized’ phone numbers for a fee. The process is the following, assuming an incoming request for a given customer and a chosen phone number:

  1. The system checks if the number is available, and if so then reserves that number for some time (on behalf of the customer).
  2. The customer’s credit is checked in the billing system.
  3. If OK, then the phone number reservation is confirmed and the billing is done.
  4. Otherwise, the phone number is released again and no billing is done.

Imagine the BPM modeling you would need to do to handle all failure scenarios and confirmation scenarios from that last 2 steps. We know from experience that this does not scale…

Instead, what we offer is a complete and reliable automation of the confirmation and cancellation steps - letting you focus on the happy path of the workflow. We do this via a service called TaaS (TCC as a Service) and plan to offer a REST implementation of that. We’ve presented this idea at the recent SOA symposium (the presentation can be found here) and we are looking for early adopters to sponsor our version one product…

So if your SOA should be lightweight and involves the concept of reservations of business resources then please email us today to apply for our early adopter program. Don’t wait, because being a small company we can only do a few of these and first come means first served…

Why Atomikos? Because we certify YOUR stack, not ours!

October 3rd, 2012

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 Developer 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.