Platform Engineering for Private Cloud
summary
Claim: about ~50% of enterprise apps run on private cloud, so platform work targets existing on‑prem stacks not greenfield public cloud. Evidence: Backstage/internal developer portals, CNCF reference architecture and Kubernetes are used but Kubernetes alone does not deliver developer productivity. Built outcomes: IDPs, developer advocacy teams (banks run ~7–8 advocates), product management and marketing practices, finance metrics and a platform as a product approach. Timeframe: adoption follows a 3–5 year adoption curve and AI becomes another middleware service to broker on‑prem.
AI-written summary · about
chapters (11)
- 0:00Platform engineering intro
- 3:45Where apps run and why
- 9:21What is a platform?
- 17:10Platform team roles
- 24:09Platform as a product
- 30:05Marketing platform adoption
- 35:46Tracking metrics
- 42:03Spreading platform use
- 45:10Platform maturity models
- 47:19Platform engineering and AI
- 50:10Q&A
related talks
42mPlatform Engineering in practice — Why and How to start
39mPlatform Engineering as a (Community) Service
20mPlatform-First Cloud Transformation
41mPlatform Engineering for Developers, Architects & the Rest of Us
33mPlatform engineering: Build your own PaaS
41mPlatform as a Product
40mLessons Learned Building Developer Platforms
11mBuilding Scalable Developer Platforms