CloudBees has purchased Stax Networks (see their write-up) to build out their ambitions to become the leading Java PaaS. Thus far, CloudBees has been known as the Hudson in the cloud company, running the continuous build tool in the cloud (on Amazon) for it’s beta users. Doing a build in the cloud is one thing, but tooling all of the activities around the build-test-deploy-run-repeat cycle is a bigger pie to eat from.
(As a minor note, by “Java PaaS” I mean “any VM-based language,” not just the Java language.)
There are many efforts underway to do “cloud ALM” though, wisely, no one calls it that. “ALM” has long been thought of as more of a bureaucratic-hell for developers than something useful. Still, for any sane organization the checks-and-balances and quality-through-process that ALM drives towards is required. It’s one thing for some slick .com to eschew ALM, but all those Toyota owners out there probably appreciate the mounds of process paperwork that ALM and higher paper-pushing practices stocked up.
As the diagram here shows, CloudBees is looking towards Stax to help them fill out the “deploy to production” part of that cloud ALM vision. I’d suggest that this “production” (the running of the code) is the area that needs the most innovation in the cloud space and is, therefore, the most difficult nut to crack. The idea of push button deployments to production is great, but the actual reality of deploying, diagnosing problems, rolling back, and so on get messy. And, indeed, solving those problems is (or should be) the value that a PaaS brings…
- CloudBees launches Java cloud (infoworld.com)
- The Value of the Freedom to Leave the Cloud: Salesforce and Heroku (redmonk.com)
- PaaS Is The Future Of Cloud Services: CloudBees Acquires Stax Networks To Accelerate Their PaaS Strategy (cloudave.com)