Everybody is talking about the cloud these days. However the term Cloud is completely over-hyped! Suppliers rebrand their products into cloud products even when it has not only one Cloud property. People say that they are using Cloud computing, but they mean virtualization… and so on.
In this article I’ll try to explain the Internal Cloud and what you need for the Internal Cloud. We also will take a look if we can build an Internal Cloud with Hyper-V and System Center.
Let’s first take a look at the Wikipedia definition of Cloud computing:
Cloud computing is the delivery of computing as a service rather than a product, whereby shared resources, software, and information are provided to computers and other devices as a utility (like the electricity grid) over a network (typically the Internet).
When you look at this definition I can imagine that you say: Hey we’re already doing this for a couple of years and that can be true. Cloud is just a marketing term!
Ok now we’ve clarified the term Cloud let’s take a look at the difference between an internal cloud and a public (external) cloud. The main difference is that an internal cloud is only dedicated to your company and a public cloud is shared with many. An example of a public cloud service is Office 365. Many companies share this platform with other companies and it’s not possible to get a dedicated Exchange server or Sharepoint server within this service. The opposite is true for a private cloud service. Within a private cloud you can get dedicated servers or dedicated hardware.
However, the question is: when are we talking about a private cloud? Well Gartner made a nice model with required en preferred components for a private cloud:
When any of the required components is missing we’re not talking about a private cloud.