Scalr being a Cloud Management company, we often blog about how Cloud Management can increase the value you get out of your cloud (in the IaaS sense of the term).
But how do you decide to use cloud in the first place? Our experience has been that the reasons for organizations to adopt or discard cloud are sometimes quite nebulous. This post seeks to provide clarity.
AWS is the Largest Cloud, but it isn’t the Only Cloud
Cloud infrastructure was invented by Amazon when the company launched its AWS (Amazon Web Services) offering. AWS’s value proposition was (and still is) characterized by:
Trading capital investments (CAPEX) for operational expenditure (OPEX), thanks to a pay-per-use billing model
Consolidating workloads and increasing utilization, thanks to virtualization that enables a vast range of diverse instance types
Providing self-service and instant access to infrastructure resources, thanks to a UI and an API that make it possible to provision instances in minutes, and thanks to a billing model based on hourly increments.
Evidently, these are tradeoffs, not straight up benefits. In fact, your organizati
on might decide not to adopt cloud specifically because you have existing capital investments (CAPEX) you intend to leverage, or because your high-performance computing (HPC) workloads can’t afford to run on virtualized hardware.
But fortunately, you don’t have to throw the baby away with the bathwater! There are options that allow you to “unbundle” this value proposition.