How Ops Can Diversify Your Application Assets
There are many harsh learnings that we experience during significant disruptions and performance issues. The public cloud seems to have been the catch-all answer for solving some of these challenges, or so it would seem. The reality of the public cloud is that it solves specific challenges in a way that has become widely embraced. There are also still a lot of shortcomings and challenges that are in place.
When is one cloud not enough? When we design our on-premises environments we are bound to more limiting factors around embracing true platform diversity at the underlying infrastructure layers. When we move to the public cloud, it seems like the right time to not just solve things like deployment velocity and scalability, and to think bigger at inception.
Designing for cloud-native environments should really be the first step on a journey to a multi-cloud architecture. Here are a few reasons why this is important and should be on the minds of every application and cloud infrastructure architect.
Multi-Cloud Advantage #1: Cloud Diversity
No matter how resilient the services that back the public clouds are, they fail. That’s a fact. If you know that there is more than a zero percent chance of failure (which there is) then we should all be architecting for diversity in the services to ensure we can have business continuity during outages.
Read the entire article here, How Ops Can Diversify Your Application Assets
via the fine folks at Turbonomic!