Why did the term cloud computing so quickly lose its original meaning? At first, cloud computing was about how to not build a data center, but it quickly morphed into an architectural description of how you should build a data center. The first definition is about accessing IT services over the Internet from computing resources that somebody else owns and operates. The second definition is about building your own hyper-efficient data center based on virtualization, shared resources, and dynamic provisioning. These definitions are so different – contradictory even – that it takes modifiers like external, public, internal, and private to tell them apart. To many, it seems that we have sunk into a morass of confusion.
My point here, though, is not to debate definitions or technology. (I believe that both internal and external clouds will be wildly successful for many years to come.)
My question today is why the definition got muddled so quickly, especially since this isn’t the first time it has happened. The original idea of utility computing was that computing should be like electricity. In the early days, companies had their own generators, but over time, centralized power companies replaced them. The theory was that IT should evolve in the same way. This same metaphor also inspired grid computing, but as with cloud computing, the definitions quickly shifted to data center architectures. I remember many data center tours where the proud owner of rack after rack of Linux nodes would say, “Check out my compute grid.”
What is going on here? I believe that IT is in denial. CEOs and CIOs are like ships passing in the night.
CEOs ask, “Why can’t we just convert to cloud computing?” What they mean is this: “I’m tired of expensive data centers, high capital costs, and hard to manage infrastructure. Why can’t someone else do all of that for us and we just buy it as a service over the Internet? You know, like Yahoo! email or Salesforce.com?” In other words, CEOs would like to outsource big chunks of IT, just like they have already outsourced big chunks of manufacturing.
And then the CIO comes back and says, “I figured it out. We can convert to cloud computing, but the good news is that we still get to build the data center and buy the IT equipment ourselves.” Ships in the night.
IT departments are so averse to the idea of having their jobs outsourced – who wouldn’t be! – that whenever someone tries to define a term to mean exactly that, they redefine it to mean a new thing that they get to build and run themselves. Perhaps soon there will be a creative new definition of external cloud that somehow means you build it yourself.
As I said above, I believe that both internal and external clouds will be wildly successful. For at least the next five years, more likely ten, most CIOs will run a hybrid model consisting of three main parts: (1) Traditional silos, where an application, a server, and storage are purchased and installed together; (2) Internal clouds, which will initially run less critical apps and grow over time; and (3) External clouds, which will also start low and move up.



