A 2017 RightScale survey* reported that 85% of enterprises have embraced a multi-cloud strategy. However, depending on whom you ask, multi-cloud is either an essential enterprise strategy or a nonsense buzzword.
Part of the reason for such opposing views is that we lack a complete definition of multi-cloud.
What is multi-cloud? There is little controversy in stating that multi-cloud is “the simultaneous use of multiple cloud vendors,” but to what end, exactly? Many articles superficially claim that multi-cloud is a strategy for avoiding vendor lock-in, for implementing high availability, for allowing teams to deploy the best platform for their app, and the list goes on.
But where can teams really derive the most benefit from a multi-cloud strategy? Without any substance to these claims, it can be difficult to determine if multi-cloud can live past its 15 minutes of fame.
Is multi-cloud a strategy for avoiding vendor lock-in?
Of the many benefits associated with multi-cloud, avoiding vendor lock-in is probably the most cited reason for a multi-cloud strategy. In a recent Stratoscale survey, more than 80% of enterprises reported moderate to high levels of concern about being locked into a single public cloud platform.
more than 80% of enterprises reported moderate to high levels of concern about being locked in to a single public cloud platform.
How you see vendor lock-in depends on your organization’s goals. For some companies, avoiding vendor lock-in is a core business requirement or a way to achieve greater portability for their applications. With such portability, teams can more easily move applications to another framework or platform. For others, being able to take advantage of vendor-specific features that save time on initial development is an acceptable trade-off for portability. Regardless of your point of view, a strategy that avoids vendor lock-in at all costs does mean that you will have to give up some unique vendor functionality.
In most cases, teams can still avoid vendor lock-in even without using multiple cloud providers. But how?
The key to staying flexible even within a single platform is about the choices you make. Building in degrees of tolerance and applying disciplined design decisions as a matter of strategy can ensure flexibility and portability down the road.
With this in mind, teams can work to abstract away vendor-specific functionality. Here are two simple examples:
- Code level: Accessing functionality such as blob storage through an interface that could be implemented using any storage back-end (local storage, S3, Azure Storage, Google Cloud Storage, among other options). In addition to the flexibility this provides during testing, this tactic makes it easier for developers to port to a new platform if needed.
- Containers: Containers and their orchestration tools are additional abstraction layers that can make workloads more flexible and portable.
Any technology decision represents some degree of lock-in, so organizations must weigh the pros and cons of depending too heavily on any single platform or tools.
So, is multi-cloud a really an effective strategy for avoiding vendor lock-in?
The bottom line is this: A multi-cloud strategy can help you avoid vendor lock-in, but it isn’t a requirement.
Implementing high availability and pursuing a best-fit technology approach are also frequently cited as a benefit of a multi-cloud strategy. But how do these hold up when it comes to real deployments and actual business cases?
This is just one of the questions that we’ll answer in our new whitepaper, Separating Multi-Cloud Strategy from Hype: An Objective Analysis of Arguments in Favor of Multi-Cloud.
You will learn:
- The reality vs. hype of multi-cloud deployments
- How to achieve high availability while avoiding vendor lock-in
- The advantages of a best-fit technology approach
- The arguments that should be driving your multi-cloud strategy
Google Cloud Platform Certification: Preparation and Prerequisites
Google Cloud Platform (GCP) has evolved from being a niche player to a serious competitor to Amazon Web Services and Microsoft Azure. In 2019, research firm Gartner placed Google in the Leaders quadrant in its Magic Quadrant for Cloud Infrastructure as a Service for the second consecuti...
New Lab Challenges: Push Your Skills to the Next Level
Build hands-on experience using real accounts on AWS, Azure, Google Cloud Platform, and more Meaningful cloud skills require more than book knowledge. Hands-on experience is required to translate knowledge into real-world results. We see this time and time again in studies about how pe...
New on Cloud Academy: AWS Solution Architect Lab Challenge, Azure Hands-on Labs, Foundation Certificate in Cyber Security, and Much More
Now that Thanksgiving is over and the craziness of Black Friday has died down, it's now time for the busiest season of the year. Whether you're a last-minute shopper or you already have your shopping done, the holidays bring so much more excitement than any other time of year. Since our...
Understanding Enterprise Cloud Migration
What is enterprise cloud migration? Cloud migration is about moving your data, applications, and even infrastructure from your on-premises computers or infrastructure to a virtual pool of on-demand, shared resources that offer compute, storage, and network services at scale. Why d...
6 Reasons Why You Should Get an AWS Certification This Year
In the past decade, the rise of cloud computing has been undeniable. Businesses of all sizes are moving their infrastructure and applications to the cloud. This is partly because the cloud allows businesses and their employees to access important information from just about anywhere. ...
AWS Regions and Availability Zones: The Simplest Explanation You Will Ever Find Around
The basics of AWS Regions and Availability Zones We’re going to treat this article as a sort of AWS 101 — it’ll be a quick primer on AWS Regions and Availability Zones that will be useful for understanding the basics of how AWS infrastructure is organized. We’ll define each section,...
Application Load Balancer vs. Classic Load Balancer
What is an Elastic Load Balancer? This post covers basics of what an Elastic Load Balancer is, and two of its examples: Application Load Balancers and Classic Load Balancers. For additional information — including a comparison that explains Network Load Balancers — check out our post o...
Advantages and Disadvantages of Microservices Architecture
What are microservices? Let's start our discussion by setting a foundation of what microservices are. Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs). ...
Kubernetes Services: AWS vs. Azure vs. Google Cloud
Kubernetes is a popular open-source container orchestration platform that allows us to deploy and manage multi-container applications at scale. Businesses are rapidly adopting this revolutionary technology to modernize their applications. Cloud service providers — such as Amazon Web Ser...
AWS Internet of Things (IoT): The 3 Services You Need to Know
The Internet of Things (IoT) embeds technology into any physical thing to enable never-before-seen levels of connectivity. IoT is revolutionizing industries and creating many new market opportunities. Cloud services play an important role in enabling deployment of IoT solutions that min...
Which Certifications Should I Get?
As we mentioned in an earlier post, the old AWS slogan, “Cloud is the new normal” is indeed a reality today. Really, cloud has been the new normal for a while now and getting credentials has become an increasingly effective way to quickly showcase your abilities to recruiters and compan...
How to Go Serverless Like a Pro
So, no servers? Yeah, I checked and there are definitely no servers. Well...the cloud service providers do need servers to host and run the code, but we don’t have to worry about it. Which operating system to use, how and when to run the instances, the scalability, and all the arch...