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
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...
AWS Security: Bastion Host, NAT instances and VPC Peering
Effective security requires close control over your data and resources. Bastion hosts, NAT instances, and VPC peering can help you secure your AWS infrastructure. Welcome to part four of my AWS Security overview. In part three, we looked at network security at the subnet level. This ti...
Top 13 Amazon Virtual Private Cloud (VPC) Best Practices
Amazon Virtual Private Cloud (VPC) brings a host of advantages to the table, including static private IP addresses, Elastic Network Interfaces, secure bastion host setup, DHCP options, Advanced Network Access Control, predictable internal IP ranges, VPN connectivity, movement of interna...
Big Changes to the AWS Certification Exams
With AWS re:Invent 2019 just around the corner, we can expect some early announcements to trickle through with upcoming features and services. However, AWS has just announced some big changes to their certification exams. So what’s changing and what’s new? There is a brand NEW ...
New on Cloud Academy: ITIL® 4, Microsoft 365 Tenant, Jenkins, TOGAF® 9.1, and more
At Cloud Academy, we're always striving to make improvements to our training platform. Based on your feedback, we released some new features to help make it easier for you to continue studying. These new features allow you to: Remove content from “Continue Studying” section Disc...
AWS Security Groups: Instance Level Security
Instance security requires that you fully understand AWS security groups, along with patching responsibility, key pairs, and various tenancy options. As a precursor to this post, you should have a thorough understanding of the AWS Shared Responsibility Model before moving onto discussi...
Cloud Migration Risks & Benefits
If you’re like most businesses, you already have at least one workload running in the cloud. However, that doesn’t mean that cloud migration is right for everyone. While cloud environments are generally scalable, reliable, and highly available, those won’t be the only considerations dri...
Real-Time Application Monitoring with Amazon Kinesis
Amazon Kinesis is a real-time data streaming service that makes it easy to collect, process, and analyze data so you can get quick insights and react as fast as possible to new information. With Amazon Kinesis you can ingest real-time data such as application logs, website clickstre...
Google Cloud Functions vs. AWS Lambda: The Fight for Serverless Cloud Domination
Serverless computing: What is it and why is it important? A quick background The general concept of serverless computing was introduced to the market by Amazon Web Services (AWS) around 2014 with the release of AWS Lambda. As we know, cloud computing has made it possible for users to ...
Google Vision vs. Amazon Rekognition: A Vendor-Neutral Comparison
Google Cloud Vision and Amazon Rekognition offer a broad spectrum of solutions, some of which are comparable in terms of functional details, quality, performance, and costs. This post is a fact-based comparative analysis on Google Vision vs. Amazon Rekognition and will focus on the tech...
New on Cloud Academy: CISSP, AWS, Azure, & DevOps Labs, Python for Beginners, and more…
As Hurricane Dorian intensifies, it looks like Floridians across the entire state might have to hunker down for another big one. If you've gone through a hurricane, you know that preparing for one is no joke. You'll need a survival kit with plenty of water, flashlights, batteries, and n...
Amazon Route 53: Why You Should Consider DNS Migration
What Amazon Route 53 brings to the DNS table Amazon Route 53 is a highly available and scalable Domain Name System (DNS) service offered by AWS. It is named by the TCP or UDP port 53, which is where DNS server requests are addressed. Like any DNS service, Route 53 handles domain regist...