3 items are of interest. The first, is naming of a cloud based on its deployment. Second, clouds can further be classified based on services it provide to users. And lastly, a case study. Think of your plan to build a cloud and how it would be shaped.
A) A cloud is named based on its location or deployment.
- Public - Applications, storage and services made available to the general public for free or for a fee.
- Private - For a single organisation and decisions made centrally on resources.
- Community - Shared infrastructure having several organisation with specific interest that is managed internally or by a 3rd party.
- Hybrid - Combination of either Public, Private or Community, or all three.
B) A cloud can then be named based on its services.
- IaaS (Infrastructure-as-a-Service)
- Users install own operating system and maintain its own patches, IP addresses. - Rackspace, Amazon EC2.
- Users can leverage resources to sell as a service provider to their clients.
- PaaS (Platform-as-a-Service)
- Run your own application on a provider's platform
- Develop on a provider's platform - Google AppEngine, Oracle Cloud Platform, OpenShift.
- SaaS (Software-as-a-Service)
- Full web application - E.g. Googledocs, SalesForce, Gmail
- Web services (consumed by other web application) - GoogleMaps API, PayPal
C) A case study
- By providing one or two standard platforms, all development can be better managed. Deployed applications can be made to meet security and other standards set.
- Many new applications/web services can be introduced by users.