Why You Can't Buy Cloud Native
summary
Claims cloud native is about how software is delivered, not the tools you buy, and you cannot “install” cloud nativeness. Shows failures: kubernetes plus microservices often produce a distributed monolith, pipelines that keep every artifact at version numbers stuck at 1.0, release boards that meet every six months, forgotten clusters costing €1,000s, a startup hit with $72,000 cloud charges and another $11,000 egress bill. Recommends deploy frequently, use deferred wiring and feature flags, treat CI/CD as practice, add SRE/FinOps and surface costs with tools like Backstage.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:56I work for Red Hat
- 3:00What is Cloud Native
- 5:42The Architecture Shop
- 8:26The Problem
- 8:47Microservices
- 9:46Distributed monolith
- 15:31Not releasing
- 17:58CICD
- 19:58Release Board
- 23:06Testing
- 23:43Enterprise Hairball
- 26:24Risk Reduction
- 28:18Story Time
- 29:26Cloud Bills
- 32:15Open Cloud Costs
- 35:44Culture vs Containers
- 36:56Legacy
related talks
20mComplexity of the cloud native ecosystem
42mCloud Native Applications
43m(Mis)Understanding Cloud-Native
32mFrom Cloud Naive to Cloud Native – Avoiding Mistakes Everyone Does
54mCloud Native Culture
03mGoing (cloud) Native
53m(Mis)Understanding Cloud Native
36mPractical Cloud Native: What Works, What Doesn't