A primary goal for the CIO since the beginning of IT time has been to keep costs low. And one area that is not always a focus of cost reduction is enterprise software development. Cloud to the rescue.
It’s all about “Platform as a Service” these days. But juxtaposed to Infrastructure as a Service (IaaS), what does PaaS mean, and how do you make the right choice for a given application? I see at least two different kind of PaaS environments addressing different scenarios and needs. It’s important, when embarking on the development and/or migration of an application to a cloud environment, to thoroughly think through which PaaS environment to use.
PaaS, a definition
Infrastructure teams tend to think shorter term and as a consequence are often ill-suited to lead cloud migrations. How do I know? I've had contact with three customers recently where the marching orders were to move quickly and invest as little as possible in the migration. The goal was to reduce costs move by shuttering data centers and manage multiple suppliers.
A colleague prompted me to make the case for OpenStack and I think it deserves deep consideration from enterprise CIOs in the midst for forumlating their cloud strategies.
Imagine having thousands of applications to put into the cloud. What are the steps to taking on such a massive project? Well, this is what I told a customer who informed me that he had five thousand apps to migrate into the cloud. I suggested a six step approach.
1) Understand the vision, establish the priorities
I don't agree with David Linthicum's post in InfoWorld that contends the IaaS and PaaS markets will no longer support smaller providers. He also argues that the little guys will have to exit those markets and find something else to do.