In part 1 of this series, I laid out the “magic cube” that describes 8 combinations for cloud deployment. The cube provides a finer grain understanding than “public” vs. “private” clouds because we can now clearly see that there are multiple technology axis that create “private IT” that can be differentiated.
The axis are: (detailed explanation)
- X. Location: Hosted vs. On-site
- Y. Isolation: Shared vs. Dedicated
- Z. Management: Managed vs. Unmanaged
In this section, we take off our technologist pocket protectors and pick up our finance abacus. The next level of understanding for the magic cube is to translate the technology axis into business vectors. The business vectors are:
X. Capitalization: OpEx vs. CapEx. On the surface, this determines who has ownership of resource, but the deeper issue is if the resource is an investment (capital) or consumable (operations). Unless you’re talking about a co-lo cage, hosting models will be consumable because the host is leveraging (in the financial sense) their capital into operating revenue.
Y. Commitment: PayGo vs. Fixed. Like a cell phone plan, you can pay for what you use (Pay-as-you-go) or lock-in to a fixed contract. Fixed is generally pays a premium based on volume even though the per unit cost may be lower. In my thinking, the fixed contract may include dedicated resource guarantees and additional privacy.
Z. Management: Insource vs. Outsource. Don’t over think this vector, but remember I not talking about off shoring! If you are directly paying people to manage your cloud then you’ve insourced management. If the host provides services, process or automation that reduces hiring requirements then you’re outsourcing it IT. It’s critical to realize that you can’t employee fractional people. There are fundamental cloud skillsets and tools that must be provided to operate a cloud (including, not limited to DevOps).
THE 3 VECTORS ARE NOT EQUAL!
If you were willing to do some cerebral calisthenics about these vectors then you realized that they are not equal cost weights. Let’s look at them from least to most.
- The commitment vector is very easy to traverse this vector in either direction. It’s well established human behavior that we’ll pay more for to be more predictable, especially if that means we get more control or privacy. If I had had a dollar for everyone who swoons over cloud bursting I’d go buy that personal jet pack.
- The capitalization vector has is part of the driver to cloud as companies (and individuals) seek to avoid buying servers up front. It also helps that clouds let you buy factional servers and “throw away” servers that you don’t need. While these OpEx aspects of cloud are nice, servers are really not that expensive to lease or idle. Frankly, it’s the deployment and management of those assets that drives the TCO way up for CapEx clouds, but that’s not this vector so move along.
- The management vector is the silverback gorilla standing in the corner of our magic cube. Acquiring and maintaining the operations expertise is a significant ongoing expense. In many cases, companies simply cannot afford to adequately cover the needed skills and this severely limits their ability to use technology competitively. Hosts are much better positioned to manage cloud infrastructure because they enjoy economies of scale distributed between multiple customers. This vector is heavily one directional – once you fly without that critical Ops employee in favor of a host doing the work, it is unlikely you’ll hire that role.
The unequal cost weights pull our cube out of shape. They create a strong customer pull away from the self-managed & CapEx vertices and towards outsourced & OpEx. I think of this distortion as a cloud gravity well that pulls customers down from private into public clouds.
That’s enough for today. You’ll have to wait for the gravity well analysis in part 3.