Public Clouds, Private Clouds, Hybrid Clouds

Tuesday, September 29, 2009

A company may chose to use a service provider's cloud or build its own.

Public clouds are run by third parties, and jobs from many different customers may be mixed together on the servers, storage systems, and other infrastructure within the cloud. End users don't know who else's job may be running on the same server, network, or disk as their job runs.



Private clouds are built within an enterprise for their proprietary use. Private clouds are good for companies dealing with data protection and service level issues. Private clouds are on-demand infrastructure built and managed by single customer who controls which applications run, and where. They own the server, the network and disk and can decide which users are allowed to use the infrastructure.

Though initially enterprises start with their own private cloud by adding a layer of new technologies to their existing data-center systems and processes, in a long run they will likely want to run applications both in privately owned infrastructure and in the public cloud space as well. Thus we have the third model of clouds.

Hybrid clouds combine the public and private cloud models. Enterprises will own parts, and share other parts, though in a controlled way. Hybrid clouds offer the promise of on-demand, externally provisioned scale, but add the complexity of determining how to distribute applications across these different environments.