Java in the Cloud: Amazon Joins the Party

Amazon announced today its Elastic Beanstalk offering, essentially providing Java in the cloud. This is great news as it reinforces the message that the future of Java is in the cloud, not on premise.

Yet, beyond the signal it sends to the market, this move doesn’t radically change the current situation. If you are a Java developer, you will find that CloudBees is a more mature and more sophisticated offering. CloudBees is a global platform, from dev to production, which will shield you from IT entirely.

Let’s dig more into how CloudBees’ vision differs from AWS’.

First of all, at CloudBees we think that for the cloud to make sense to developers, it needs to provide a proper answer at all stages of an application’s lifecycle, not just at runtime deployment: code and binary repositories, building, testing, continuous integration, deployment, maintenance, integration with 3rd party systems, etc. We want multiple developers to be able to work as a team on those projects, we want them to know who is doing what, and for the more sophisticated deployments, what staging process needs to be followed before the new version of an application gets pushed to production. We don’t want you to even care about scalability, high-availability or any other IT related issue, we will handle that for you – “servers” are not what’s going to make your applications differentiated business-wise – let us handle that part. Also, let us live patch our platform so it is always the most performing and secure service you can find on the market.

Also, we see a lot of companies afraid about vendor lock-in, and this gets even more sensitive as they consider the cloud as their new platform: not only do they have to care about the software they leverage, but they also need to care about the cloud infrastructure they’ll rely-on as well as the 3rd party services they’ll closely integrate with. At CloudBees, all of our services are either based on Open Source and/or Open Standards: Java, Java EE, Spring, MySQL, SQL, etc. In terms of cloud infrastructure, CloudBees is IaaS-agnostic. We think the choice of a specific IaaS vendor should be up to the customer, either for legal issues or because they might want their Java CloudBees deployments to be collocated with other non-CloudBees deployments

Lastly, much like we think the cloud is the new platform, we believe SaaS vendors are the new ISVs. ISVs are morphing into SaaS vendors and, as part of this transition, the old model of ISVs certifying on top of operating systems and middleware vendors and leverage them as their preferred go-to-market channels doesn’t apply anymore. The new go-to-market for those SaaS vendors are the cloud-native PaaS, and only the PaaS with a partner-friendly approach can succeed, both at the back-end layer (IaaS) as well as at the front-end (PaaS extensions, 3rd party services, etc.). CloudBees is a partner-friendly environment; we are easy to do business with.

This is what we are delivering with our DEV@cloud and RUN@cloud offering and vision, all smoothly integrated.

As the Java expert, CloudBees provides depth and precise understanding of what Java developers’ needs are, coupled with our leading vision of where the cloud is going.

Who said Java was dead?
 

Onward,
Sacha

P.S.: and remember, we will provide a fully integrated CloudBees+Stax offering by the end of this month!

Sacha Labourey, CEO