Archive for the ‘Solutions’ Category

On the cost of the appserver

Tuesday, July 13th, 2010

Here is another excellent article about the cost of application servers, and why a paradigm shift is needed with lighter-weight alternatives:

http://www.tomcatexpert.com/blog/2010/06/03/migrating-jee-applications-tomcat-motivation-migrating

Interesting note: the author used to work at Bea, so he definitely knows what he is talking about;-)

Light-weight JEE webapps

Monday, July 12th, 2010

Check out http://www.tomcatexpert.com/blog/2010/07/07/how-migrate-jee-applications-tomcat for a nice discussion on how to migrate from jee to a light-weight alternative like Tomcat - with Atomikos for JTA if needed.

Of course, you can also use Jetty from Webtide (which has Atomikos pre-integrated into the Hightide edition)…

Integrating Atomikos with JPA/Hibernate, Spring, Infinispan and GWT

Tuesday, June 15th, 2010

Check out this cool blog entry on how this can all work together.

DISCLAIMER: the suggested solution has not yet been verified by Atomikos…

Atomikos: Reliability for the Cloud

Monday, May 10th, 2010

The cloud phenomenon is an interesting one, and a natural evolution of the outsourcing model. While a lot is going on around cloud computing itself, little is being said about reliability.

Do clouds offer reliability? In a way yes: caching systems like Terracotta, Gemstone or Oracle’s Coherence offer a fail-safe mode for availability of your data in the form of caches. So if a cloud node goes down, chances are that a live copy of the data still exists somewhere else, which means that your process can continue working elsewhere.

All is fine (or mostly fine) if you are working with a single database and are processing, say, web requests in the cache. After all, if you only have one database and no other resources then you don’t even need something like a transaction manager (or Atomikos, for that matter). There are at least two situations where things change:

  • If you queue cache updates to enable write-behind, then you find yourself in a queuing scenario and are processing jobs from a queue to a database. Enter distributed transactions.
  • If you are not processing web requests but rather get queued requests from the start. Enter distributed transactions.

In both cases you should at least consider using a transaction manager. In both cases, Atomikos is a good choice for the following reasons:

  • It’s open source (or at least our basic version is)
  • It’s very light-weight and easy to deploy (meaning it lends itself easily to cloud-oriented virtualized configurations)
  • It bundles over 10 years of experience and market leadership
  • It provides full crash recovery and all other bells and whistles - unlike many of the built-in solutions that you will find in a cache

So in that way, Atomikos provides “reliability for the cloud”.

Quick Update: Maven

Thursday, April 8th, 2010

Our maven integration has not been the most fluent thing we ever did, but we now seem to have gained some traction in the right direction (thanks to community hints, some solid teamwork and hours of additional brain-storming). Here is a quick update on where we are:

  • Upload to maven central is working but not yet optimal (we’re working on that).
  • Meanwhile, we’re also re-evaluating our entire build environment to optimize for maven builds (i.e., switching from ant to maven entirely).
  • We’re also restructuring our SVN repository so it has optimal support for our business model.

As you can see, we’re not afraid to throw away anything in our quest to improve things :-) Contrary to what I expected, going from ant to maven seems to simplify our build after all: maven seems to be maturing, and new team members tend to know maven better than ant.

All these changes have quite some impact on the architecture of our build ecosystem, so we can’t just do them overnight. However, we would like to have them ready before we bring out the next major new release(s).

Thank you for your patience!

Configuring Hibernate JPA+Infinispan+Atomikos

Monday, February 1st, 2010

Here is an interesting post at JBoss about configuring Hibernate, Infinispan’s caching and Atomikos JTA (among other JTA implementations). Sample code and configuration files are included.

Regards

Fabric3 (SCA) Integration of Atomikos TransactionsEssentials

Wednesday, December 2nd, 2009

Those of you who have been watching our RoadMap know that SCA is one of the topics on our list of things to watch.

Well, it turns out that the team of Fabric3 has been integrating TransactionsEssentials into the Fabric3 SCA runtime. Nice work!

Atomikos in Skyway YouTube Video

Tuesday, December 1st, 2009

Check out this cool video to see how OEM customers are using Atomikos to build mission-critical applications with out-of-the-box reliability outside the application server…

Also, check out the Skyway toolset if you have a chance - it is pretty awsome :-)

Increase Reliability and Decrease Costs

Sunday, September 27th, 2009

This article on infoworld about last Summer’s outages is a typical illustration of how things can go wrong in a networked business world. With the current recession, cost cuts and commoditization of both software and hardware, the end result seems to be converging towards the state predicted by the late Jim Gray during his Turing Award speech in 1998:

“Cheap and buggy. Sometimes it will work, sometimes not, and nobody will really know why”.

Given the perspective of such a world, it seems like some precautions are justified. Since it can’t be repeated often enough, here is the Atomikos view on how to alleviate all this:

  • Use our transaction technology to avoid data inconsistency after a failure or crash. It acts like an insurance, really: you don’t need it when things are fine, but when things are turning bad you’re sure glad to have one!
  • Use queuing to your advantage. Avoid depending on the availability of a remote service by delaying requests until they can be performed (i.e., when the remote service is up).
  • Add virtually unlimited scalability while you’re at it…

The combination of technologies and techniques outlined here will increase your reliability while decreasing costs. You save on expenses by using commoditized hardware and software. You also save on man-hours of development because our products will allow you to focus on the happy path (failure handling is automated to a large part by our software). This significantly decreases the complexity of the workflow your developers have to code, maintain and debug. Less code in turn means less bugs, so this again increases reliability. Isn’t that beautiful?

Atomikos inside web containers

Monday, June 15th, 2009

Are you looking for an open source JTA/XA transaction manager for your web container?

Although web apps are not our mainstream business, some people do value Atomikos for their web apps.

See the jetty wiki for information on how to configure Atomikos within Jetty.

See this wiki page for configuration of Tomcat and Atomikos.