Platform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
summary
Internal platforms often bloat with redundant tools — one cited enterprise buys 200 unused licenses — so the proposed fix is an opinionated, five-step platform: developer portal (Backstage), shift-left security, CI/CD+IaC+feature flags, resilience (Litmus/chaos), and observability/cost (Prometheus/Grafana/OpenCost). They assemble existing OSS into an enterprise-grade stack (K0s, Cluster API, Sveltos, Karmada) branded as a multicluster IDP that claims to eliminate vendor lock‑in and deliver AI‑ready clusters.
AI-written summary · about
chapters (16)
- 0:00Welcome
- 3:10Modern cloud complexity
- 7:47Why platform engineering
- 11:21Bloated platforms downsides
- 15:56Infrastructure as code
- 17:22Democratic platforms
- 18:05Five steps to platform
- 22:18Platform evolution recap
- 23:20Multicluster sovereignty
- 26:27Open source multicluster K8s
- 29:54Distributed infrastructure pillars
- 31:00Cluster management tools
- 33:28Kubernetes generations
- 35:14AI-ready clusters
- 36:22Platform engineering goals
- 38:27Quiz and closing
related talks
37mPlatform Reality Has a Surprising Amount of Detail
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
44mPlatform Engineering 101: Building Internal Developer Platforms
37mPlatform Engineering's Inferno
25mInternal Platform as a Product
26mBuilding Internal Platforms to Enhance Developer Experience
46mBeyond DevOps: How and Why Companies Converge on Platform Models
11mBuilding Scalable Developer Platforms