So you're into REST and you are wondering how to define some kind of transaction guarantee with it…

Look no further, because we have exactly what you need:

• A design pattern
• A simple, vendor-independent REST API
• Backed by a reusable coordinator service if you need one (that is up to you, really)

FREE download: "TCC for REST API" (API specification)

PS: the technology described in this specification is available and can be downloaded as part of TransactionsEssentials

Interesting independent survey: 68% uses a web container like Tomcat or Jetty.

Credit for the survey is due to Zero Turnaround

Again, some solid 3rd party confirmation that we were right about JEE without application server

Suffice it to say: we're one of the first ones to modularise and open up the APIs of JEE…

Today is a big day for us: we've published our new pricing model. It's simple, clear, and most of all cloud-ready because there is hardly any counting of CPUs or cores. Since nobody can know these things in a cloud, it's no use trying to count anyway.

Of course this didn't just fall out of the sky: we've spent most of the previous year talking to prospects and customers to find out what works for them and what doesn't. The result, we think, is worth blogging about. We can't wait to learn what you think…

Enjoy!

PS thanks to all those customers and prospects who have given us useful feedback to make this possible!!!

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.