By RickG on Mar 21, 2014
The next area of Cloud computing subject to the distorting effect of orthogonality has to do with the way many people want to start to use the Cloud. The most common starting place is to try to move existing applications to the Cloud.
People want to migrate an existing application to a new environment. Migration, by its very nature, is orthogonal. In a migration effort, you invest effort and resources and take on risk to achieve the goal of having the same application you used to have. So there are costs for the migration effort, without an direct benefit over what you have now from that effort. Of course, there are other benefits that come from a migration, such as a simpler or most cost-effective environment, but these are not directly related to the migration itself. This is the definition of orthogonality – benefits from one area and costs from another.
However, the hope that a migration to the Cloud will be effortless is founded on a basic misconception about the Cloud. The Cloud is not magic – reduced costs are not suddenly available through magic Cloud pixie dust. Although Cloud vendors may get their underlying components at a bigger discount because they buy larger quantities, this savings is offset by the need for these companies to make a profit on their services.
The way the Cloud saves money is through automation. Cloud vendors automate various IT maintenance tasks and operations, and, by doing so, can scale with less expense. Pretty much all the cost benefits from the Cloud stem from this core fact. Even a technical feature like multi-tenancy is a way to automate the support of many individual tenants on a fixed pool of IT resources.
The use of automation comes with a corresponding loss of flexibility. Automated procedures expect fairly standardized environments, or they may not work properly. The more productivity that a Cloud offering provides, the more automation, the greater the loss of flexibility.[Read More]