Symmetric multi-cloud deployment Strategy
When I say symmetric multi-cloud deployment strategy I mean you are deploying the same workload in two or more public cloud providers and on to your private data center at the same time with the same CICD. In this case life will always be easy, if you are dealing with IaaS or K8's clusters. PaaS may not be ideal as most of the time it will be purpose built platform. I am not even talking about SaaS.
Why do you need symmetric multi-cloud model
Bursting: Private data centers first and cloud to burst is the best use case for leveraging any public cloud vendor, that way still the keys to kingdom will be in your hand.
Price negotiation: You can confidently negotiate the price with public cloud vendors and it doesn't take lot of time to switch in worst case scenario.
Do nothing cost: Lets say in case of situations like COVID you can quickly ramp down all the public cloud billing and stick to your private data centers. Imagine you are Uber and COVID hit your trends, if majority of your workloads are in public without elasticity, you will end up paying huge bill without usage and revenue source.
Another important point you need to keep in mind for symmetric multi-cloud deployment is Egress cost. This could be very dangerous in the long run and public cloud providers can exploit by pulling this lever. Keep in mind egress charges, Data going into cloud is always free, Data coming out is always charged. At this point the charges might look cheaper, but this can always fire back.
AWS will charge $0.06 – $0.09 per GB of outbound data (i.e., data transferred from your cloud infrastructure onto the Internet), whereas Microsoft Azure will charge between $0.09 and $0.13 per GB of outbound traffic. In case of GCP it is $0.08 to $0.12.
20% of enterprises employ multiple public clouds in 2017, up from 16% in 2016 (a 25% growth rate). I am expecting it to grow to 75% in the long run.
Reference:
Comments