By Seth Patterson, ViaWest Executive Director of Client Architecture
Cloud computing is ideal for businesses looking for scalability, instant provisioning, virtualized resources and the ability to expand the server base quickly. Within the three cloud service models (IaaS, SaaS and PaaS), there are basically two types of IaaS clouds: public clouds and private clouds. This blog explores the differences between public cloud types and when to use each to maximize results. My next blog post will look at private cloud types.
Before any cloud implementation, clients should perform an application assessment to:
- Understand application state and dependencies for cloud design options
- Document the processing requirements of each application (or application class)
- Identify security and compliance posture and needs for these workloads
What is a “Public Cloud?”
There are many different types of “public” clouds in the market. Most people are focused on what the major hyper-providers can offer, like Amazon Web Services or Microsoft Azure, as the top examples. There are also public clouds that are more like “community” clouds where providers offer a shared cloud environment with secure multi-tenancy, but in a more managed environment with many services offered standard and optional. The true value of the hyper-provider cloud model is that there is an extensive and constantly evolving product catalog that allows a company to add many technical service layers into their applications or environments. It is designed at such a scale that the bursting of workloads for minutes or hours can be easily done as there is ample capacity for that flexibility.
Consider a hyper-provider public cloud solution for these scenarios:
contract – a true “pay as you go” model
Consider an alternative public/community cloud in some of these scenarios:
The chart below illustrates typical application workloads and where they are often heading: