Cloud Zone is brought to you in partnership with:

Markus is a Developer Advocate at Red Hat and focuses on JBoss Middleware. He is working with Java EE servers from different vendors since more than 14 years and talks about his favorite topics around Java EE on conferences all over the world. He has been a principle consultant and worked with different customers on all kinds of Java EE related applications and solutions. Beside that he has always been a prolific blogger, writer and tech editor for different Java EE related books. He is the Java Community leader of the German DOAG e.V. and it's representative on the iJUG e.V. As a Java Champion and former ACE Director he is well known in the community. Markus is a DZone MVB and is not an employee of DZone and has posted 195 posts at DZone. You can read more from them at their website. View Full User Profile

From XaaS to Java EE – Which Damn Cloud is Right for Me in 2012-13?

12.06.2012
| 3146 views |
  • submit to reddit

Have you ever wondered what it takes to get your Java EE up and running somewhere? I did. For years. Started with hosting my own, moved on to some hosting offerings and finally stumbled upon the PaaS movement. Honestly I didn't take all that too serious. I simply wanted to run my stuff somewhere and didn't care too much about the solution. That changed over the past couple of months with the emerging offerings around. Especially with the many different offerings which label themselves XaaS. Seems to be the right time for a closer look.

From XaaS to Java EE – Which damn cloud is right for me?

(c)2012 msg systems ag

Ever single presentation on that topic starts with a general overview about XaaS offerings and how they compare. Given that I believe that there is still some need to introduce the different four letter acronyms. This nice little picture originated in kind of an innovation project done for my company. It basically tells you all you need to know about XaaS. Starting from the plain iron (IaaS, Infrastructure as a Service) you go up the latter to candyfloss (SaaS, Software as a Service). Somewhere in-between is PaaS (Platform as a Service) which basically addresses some kind of pre-packaged stack to manage and run you applications on. And this category is exactly the one where you would fit application platform like Java EE in. I'm not going to drill that further down. There is plenty of theory around different sub-categories for PaaS. I simply don't care about that because I'm not willing to write a master thesis but a practical guide.

PaaS isn't PaaS. The Selection process and the Candidates
What I do want to do is to separate the many available offerings a bit. I decided not to accept anything but offerings with a clear and certified pre-configured Java EE container. This is the reason why you will not find GAE or CloudFoundry or heroku in here. They all offer some kind of Java application hosting but no Java EE container. Here are the candidates.


Amazon ElasticBeanstalk

Amazon Web Services (abbreviated AWS) is a collection of remote computing services (also called web services) that together make up a cloud computing platform. One of them, Amazon Elastic Beanstalk provides quick deployment and management of applications in the cloud. Running Tomcat 6+7 only doesn't qualify for this shootout normally. But I am making an exception here because it is the most well known cloud offering and one of the oldest ones. Lets look at it as kind of a reference in this comparison. Register your account via aws.amazon.com/elasticbeanstalk/

Oracle Cloud - Java Service

One of the new kids on the block. Announced two years back at Oracle's annual trade fair it is now slightly rolling out to the public. Honestly I don't have an account at the time of writing but I participated in the early access program and had a chance to test it extensively. The Java service is only one part of the extensive offering. It basically comes down to a WebLogic Server to host your applications on. Access it via cloud.oracle.com.

CloudBees RUN@cloud

One among the established providers. CloudBees was founded in early 2010, is incorporated in the United States and lead by a couple of former JBoss, Oracle and VMware people. Their most prominent move was to join the JCP (Java Community Process). They offer a Java EE Web Profile stack based on JBoss AS 7. Learn more about their offerings on www.cloudbees.com

RedHat OpenShift

OpenShift is Red Hat's free, auto-scaling Platform as a Service (PaaS) for applications. This includes many different stacks for many languages. One among them is the AS 7 with the Java EE 6 Full Profile features. You can find all offerings on openshift.redhat.com

Jelastic

I meet the guys two years back at JavaOne. A very tiny booth and they were handing out business cards with trial codes on them. It has been a ride for them since then. DukesChoice Award winner this year and more and more hosting providers as partners. Beside the Java EE offering (GlassFish 3) they also run jetty and Tomcat in the cloud. Find out more at jelastic.com

SAP NetWeaver Cloud

This wasn't on my initial list but some of their developer advocates pointed me to the Apache Virgo based Java EE Web Profile offering they have. Enough to find out more and add it to the list. Find out more bit.ly/sapnwcloud

The Rating
Now that we do know a little about the candidates it is time for a first look at the rating. First assumption I made was that I am comparing the different "free offerings". So this might not completely reflect the truth if free and purchased tiers do differ too much. The one exception is Amazon. They don't offer a free tier.

One remark: I have been asked to include SLA or pricing information in this rating. I decided not to do it. The reasons are obvious. The focus was on functionality and the free offerings. Looking into pricing would open another door I am not willing to open as of today.
The rating happened with 35 individual metrics ordered in five different categories:

Administration (10)
Metrics that describe the registration process and the overall experience with instance creation and configuration. It also weights the accessibility of pricing information and the time it takes to get the environment up and running.

Development (11)
This category contains metrics around the number of different servers products, Java EE features (WP, FP), included services (e.g. database), SDK behaviour, Security, custom JVM args and more.

Deployment (7)
Metrics asking for IDE support, build support (maven, ant), usability of the web consoles and access to logfiles.

Operations (4)
Captures some few metrics around monitoring.

Ecosystem (3)
Weights in the available support options and community sizes and activity.

Given the distribution of the metrics this is clearly administration and development centered. I didn't weighted this further because I simply like it to be like this. Every metric had three different characteristics where one was assigned. Depending on the question most of them could be answered following the following scheme:

0: Not possible / low end / Unusable / Slow / No
1: Average / Usable
2: Top notch / Fast / Yes


The Results at a Glance

After everything has been ranked there was a total of 70 points (100%) to achieve.


Jelastic clearly leads the crowd here with 73 % of the possible points. Direct follower is Cloudbees with their RUN@cloud offering. OpenShift takes the proud third place in this ranking. The detailed and normalized breakdown by category reveals where everybody has it's strength and weaknesses.

Summary and Outlook

I know that this rating has very few concrete data-points to hold on to. And I'm going to disclose them over the next few months. I am also willing to do a more detailed review of the individual candidates. So consider this as a first round for late 2012 which will get updated during the next year. Happy to read your thoughts and ideas!


Published at DZone with permission of Markus Eisele, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Comments

Naiden Gochev replied on Thu, 2012/12/06 - 9:19am

Very helpful and great idea. Thanks for the info.

I hope an article like this will appear for any Java web containers(with vmware cloud foundry and etc) maybe one for .net peoples and PHP and/or RoR clouds as well it can be very helpful.

John Quinn replied on Thu, 2012/12/06 - 2:02pm

 Do you have the "Development" and "Deployment" headings switched? If so, which one has a weight of 11 and which one has 7?

Paul Kofon replied on Thu, 2012/12/06 - 4:33pm

Good write-up although the "Development" and "Deployment" headings appear to have been switched.I was almost certain that Jelastic would top the list but I resisted the urge to quickly scroll down to see the results without reading the article first.

My company recently needed to deploy an existing (non-trivial) on-premises application to the cloud. We looked closely at OpenShift, CloudBees and Jelastic as we wanted to deploy our application without having to change a single line of code. Heroku and CloudFoundry didn't really cut it. In the end we decided to go with Jelastic even though CloudBees also appealed to us.

Some of Jelastic's features that influenced our decision:

1) Setting up the deployment environment (Tomcat 7, PostgreSQL, Java 7, SSL, IP addresses) was a snap. Deploying our application and moving over the existing data took less than an hour. Nearly all of that time was spent moving over the data. 

2) We could deploy our application as it was together with all its dependencies e.g. Quartz Scheduler and Eclipse BIRT.

3) We could specify how we wanted the system to scale resources available to the application.

4) Pricing and billing information was very clearly spelt out and we could easily estimate on-going costs - this isn't easy with OpenShift.

5) Impressive performance

6) Support? My only experience was when I asked for the time on the server to be changed as it was about ten minutes late. Instead they changed the Timezone, thinking that was what I had wanted! It took four more days to make them realise the time on the server was still wrong and that the Timezone wasn't really the problem.

We evaluated it for two weeks (free of charge) before finally going into production a couple of months ago and so far things have been good.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.