Amazon Web Services (AWS), Azure, and Google Cloud Platform (GCP) are the public cloud market leaders, but how do
you determine which of them best supports the specific needs of your enterprise? For a majority of enterprises,
and for the foreseeable future, it’s going to be a multiple answer question.
predicts that “…A multicloud strategy will become the common strategy for 70% of
enterprises by 2019.”
Considering that multicloud accounts for less than 10% of enterprises today (according to the same report), that
would mark a significant increase of adoption in a very short time, even by fast-paced technology standards.
However, according to a recent study by Microsoft and 451 Research, nearly a third of
organizations already work with four or more cloud vendors.
So, the evidence is there. The experts are predicting it. How did we get here? It starts with one of the oldest myths about cloud computing: “We need one
cloud strategy or vendor.” That’s not necessarily true.
On the one hand, it can be argued that working with one vendor simplifies your work, since:
- Your IT team ought not to be platform diverse
- Middleware is highly cohesive
- The decision-making process of what services to use is simpler, since the service spectrum is defined by
your single, chosen provider
- It’s easy and comfortable for you, but especially, for your vendor
On the other hand though, your cloud attachment exposes you to a variety of issues, such as:
- Cloud data center outages
- Bandwidth problems
- Vendor lock-in
- Significantly diminished power to successfully negotiate pricing and/or business disagreements
- Opportunity cost
But as always, the most obvious point for not sticking with
a single vendor for ANY service, is that the same service type from an alternative vendor might better suit your
case – and cost less.
Of course, you should not diversify for diversity’s sake. If your strategy isn’t thought through, dealing with a
bunch of different vendors could cause more headaches than it relieves. The same holds true for going to
the cloud for cloud’s sake.
So, how do you know whether it’s time to diversify your cloud strategy? This is actually the
simplest part of the whole process, as it essentially comes down to two main reasons:
- Your current cloud costs are higher than you planned/wanted
- New requirements demand a new set of services, that may or may not offered by your current provider
For example, one of our clients underwent a 3+ year migration to AWS from on-premises. Five years later, they’re
still enjoying a close relationship with the cloud provider and satisfied with the variety of services offered.
Nevertheless, unexpected high bills and new requirements challenged the status quo.
New requirements dictated an Identity Cloud solution, as well as an API management platform. At the time,
specific requirements to the solutions weren’t satisfied by AWS offerings. Luckily, Azure seemed to offer
exactly what they needed.
The lesson? Your specific, evolving requirements, and business environment will drive
your need for diversity.
A few years later, that same client once again reevaluated their needs, and it was clear that Azure Active
Directory (AD) no longer supported their case, while Azure API management still served them well. So, they
dropped Azure AD, but kept another service in Azure.
Already exposed to multicloud, the customer sought advice on unexpected high costs in AWS. We analyzed the case