I made an easy to understand definition of what internal (private) cloud and public cloud are. As I mentioned in my previous entry, I personally believe that we will see more and more internal cloud projects coming up in the market soon. Once this step is done, people will start connecting their internal clouds to each other or to external clouds. Then this will be the real cloud hype; a mix of internal and external clouds.
I think a sushi piece is a quite good example of an internal (private) cloud. Because it is a unit, which consist of server, storage, network, power& cooling, management software, infrastructure consultancy and support services and they all work perfectly together. Since business is changing because of some reason; competition, market regulation or any other reason, internal clouds will not be enough for business requirements. Once people need to connect it with other cloud stacks in the future, other internal and/or external clouds, then they will create their own plates, depending on their requirements, filled by different types of sushis, which will work perfectly with each other.
What a brillant anology – thank you! I found a great video on this topic which gives a framework of questions to evaluate if a business should take their application(s) to the Cloud and how to assess whether to have a public cloud, a private cloud or a hybrid solution [regardless of who is providing the cloud i.e. Amazon, SalesForce, Windows Azure]
“Bridging the Gap from On-Premises to the Cloud” by Yousef Khalidi:
http://microsoftpdc.com/Sessions/SVC20
thoughts?
hope that helps,
-cn
Thanks CloudNinja. I really liked the FedEx example. It was a nice presentation.