There is a temptation to think that all cloud operating models are alike and are driven by interest in commodity IT, or IT delivered at the lowest possible cost. For many (especially early) cloud customers this is certainly the case. I predict, however, that hybrid cloud will be driven by very different operating expectations, driven by new solutions that set new IT productivity standards. It will be driven more by value-added IT, or IT services delivered at the highest level of productivity and speed. That core conviction has a great deal to do with how we came up with the name CloudVelocity.
The current popular forms of cloud can be difficult to enter and even more difficult to depart. Plenty of risk-prone and frustrating manual processes are in between the promoted economics of public cloud and the real economics of public cloud. In the case of cloud and even with the occasional outage, the journey may be much riskier and costlier than the destination.
That is why I found Anand’s blog on hybrid cloud requirements so relevant to the cloud definition discussion. There will likely be many cloud vendors who see hybrid cloud as simply adding a public cloud to a data center and perhaps a private cloud. They view private and public clouds as complimentary.
A major point about hybrid clouds that some will likely miss is that they are synergistic. A hybrid cloud is the product (not the sum) of the seamless integration of data centers and public and private clouds. A hybrid cloud enables a new generation of cloud migration, cloud devtest and cloud failover solutions.
That’s why I was also grateful to see our VP of Engineering post his recent blog about cloud devtest and why the cloud could be an especially powerful game changer for app developers. Again, that takes us to a true hybrid cloud, or the ability for apps and services to run without modification across data centers and clouds.