Complexity of the cloud native ecosystem
summary
Argues that cloud native is the best architecture for digital disruption, warns of real operational complexity around Kubernetes and the CNCF landscape, and gives concrete guidance: use Docker for small/dev and Kubernetes for everything else, Portainer spent $10M over two years on Kubernetes management tooling as proof building is costly, prefer buying off‑the‑shelf unless differentiation requires building, expect scarce cloud‑native devs, adopt multi‑tool platforms (eg Red Hat OpenShift) to avoid upgrade and integration hell.
AI-written summary · about
chapters (7)
- 0:00Cloud native disruption
- 3:54Cloud native architecture
- 9:08Build versus buy for apps
- 11:15Kubernetes complexity
- 14:46Day two operations
- 16:31Kubernetes true complexity
- 18:59Business value focus
related talks
08mKeynote: Kubernetes and Cloud Native: The Past, Present, and Future
23mIt's Dangerous To Go Alone, Take This! Navigating the Overworld of Cloud Native and Open Source
43m(Mis)Understanding Cloud-Native
42mWhy You Can't Buy Cloud Native
47mDo We Really Need Kubernetes? A Tactical Guide to Cloud Native
23mMaking Cloud Native Computing Universal and Sustainable
07mon the State of Distributed Computing
04mBuilding cloud-native applications with Kubernetes and Istio