Panel: Navigating the Path to Platform Engineering...
summary
Organizations report platform-as-product work built on Kubernetes and GCP, with one platform supporting 30,000 developers, but adoption fails if developers don’t see immediate value. Teams ship CI/CD templates and attempt gitops migration and discover migration is the hardest part—templates break when ownership moves and require manual rollout. Success metrics focus on deployment time, developer satisfaction and cost savings (idle cluster shutdowns), and platforms that start as co-built solutions or consolidate compliance tools win adoption.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 1:01Defining platform engineering
- 3:11Platform flexibility
- 3:24Strategy, adoption, and metrics
- 27:07Community and collaboration
- 30:49Compliance and business value
related talks
33mMeasuring the Impact of Platform Engineering
26mLessons Learned from 7 years of Running Developer Platforms
30mPlatform as a Product
19mKeynote Talk: Platform as a Product: Are We Nearly There Yet
46mBeyond DevOps: How and Why Companies Converge on Platform Models
27mConveying the Importance of Platform as a Product in the Cloud Native Ecosystem
32mPlatform Engineering Is Not About Tech
15mKeynote Engineering Success The Blueprint for Effective Platform Adoption