MultiCloud
summary
Panelists argue that multi‑cloud is driven by executive demands for business continuity, not easy portability; AWS and Azure dominate while GCP lags. They give concrete tradeoffs: cross‑cloud hops cost latency — on‑ramp ~2 ms versus on‑prem 20–40 ms — and outbound bandwidth fees bite when traffic exits one cloud and enters another, effectively an egress fees double hop. Tooling reality is specific: Kubernetes, EKS/AKS/GKE, Terraform, CloudFormation and ARM matter, serverless on Kubernetes shows little large‑scale traction, and overall multi‑cloud is painful and often hybrid.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:15Meet the Panel
- 3:20Why MultiCloud
- 5:18Workload Portability
- 8:55Crosscommunication
- 12:35Network
- 14:50Traffic Flow
- 18:47Security
- 20:43Serverless
- 22:25Developer Mindset
- 23:22SingleCloud vs MultiCloud
- 31:13Operational Challenges
- 33:24Barriers
- 36:24Developers
- 40:47Legacy Debt
related talks
38m50 Shades of Multi-Cloud Infrastructure
43mMulti Cloud Strategy, A Necessary Evil For An Enterprise
33mKubernetes-Driven Multi-Cloud Deployments: Maximizing Scalability and Flexibility
41mAn Adventure in Multi-Cloud with Kubernetes
20mShould we multi-cloud?
43mLeveraging Multi-Cloud Clusters in Real-World
45mMulti-Cloud & On-Premise, Let's Cross Borders! Get the Best of Both Worlds
31mMulti-Cloud Strategy in Practice