Platforms aren't tools, they are experiences
summary
Claim: platforms are experiences not just collections of tools, and Kubernetes is a foundation not a platform. Evidence: examples of Heroku, Helm installs that bring up Prometheus Grafana cert‑manager and SonarQube, and the operational pain points platforms must solve—incidents, onboarding/offboarding, compliance, test environments. Concrete build: an open source cradix framework that stitches Kubernetes, Backstage, Crossplane and SaaS to deliver self‑service “as‑a‑service” interfaces; outcome is a reusable engineering product rather than ad‑hoc scripts.
AI-written summary · about
chapters (8)
- 0:00Platforms as experiences
- 1:21Platform engineering buzzwords
- 4:50Platforms as a service history
- 6:59Kubernetes foundation
- 9:05True platform experience
- 11:34Stitching complexity
- 13:41Cradix framework
- 14:03Closing & Q&A
related talks
29mYour platform is not an island: building a platform for your ecosystem
34mComposable Platforms: Modular Platform Engineering With Kratix and Backstage
06mKeynote: PlatformOps: It’s all about Developer Experience
26mLessons Learned from 7 years of Running Developer Platforms
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
22mBuilding Platforms With Empathy and YAML at the LEGO Group
37mPlatform Reality Has a Surprising Amount of Detail