Multi Cloud Challanges Review
Download as PPTX, PDF2 likes405 views
The document outlines the high-level challenges associated with managing multi-cloud environments, particularly regarding automation, procurement, security, and backup strategies. It emphasizes the importance of data accuracy and performance across different cloud platforms while considering failover and redundancy strategies. Key considerations include network latency, operational procedures, and the complexity added to DevOps teams.
Related topics:1 of 8
Downloaded 13 times
Multi Cloud Challanges Review
- 1. Multi Cloud Challenges Review Omid Vahdaty , Cloud Architect
- 2. High Level Challenges ● Management of multi cloud services and servers from single GUI ● Automation (CI , CD, CT) ● Procurement, Accounting, and Billing ● Network considerations of HA ● High level motivation : ○ Active/Active HA on multi cloud ? ○ Active/Passive DR multi cloud?
- 3. Understand your application ● What stays the same: ○ Should run the same on all cloud: Services or servers? ■ IaaS ■ PaaS ○ Same operational procedures on all clouds ● What changes ○ Security ○ Accounting
- 4. Testing on multi cloud ● Performance ○ Mostly load balancer ○ NoSQL DB and In memory (redis) ● Data accuracy ● Usability ● backup cloud platform is expected to fall a bit short in performance since it's intended for temporary use, but data accuracy must be on the money.
- 5. Cloud Redundancy & Failover strategy ● Think about ACID ○ How to ensure data won't be lost during a switch from one cloud to another ○ Strongly Consistency? Eventually consistent? ○ Isolation? ○ Durability - Persistence - ■ RAM - not durable. ■ Disk? - may perform less. ■ Hybrid? May lose several second.
- 6. Cloud Redundancy & Failover strategy ● think through your data sync operations (synchronic, synchronic, qurum, replicas etc). ● Network Latency … :( ○ Geographic (cross continent vs. cross city) ○ WAN latency across datacenters ○ LAN latency across datacenters ● Failover ○ Application layer failover? Or DevOPS layer failover? ○ Time to fail over? 20min? >1H? > 1D? ○ Graceful failure?
- 7. Cost ● Data: If collocate all your data - it is not going to be cheap :( ● Compute: elastic ● HR: Will increase complexity of your DevOps team ○ Headcount ○ DevOps Skill set of 2 cloud vendors...
- 8. Stay in touch... ● Omid Vahdaty ● +972-54-2384178