Platform as a Product
summary
Claims that platforms are a social and technical exercise and must be treated with a product mindset drive the talk: build a minimum viable platform, focus on self‑service golden paths that move code-to-deployment, and prefer thin, replaceable components (Kubernetes as replaceable runtime). Concrete examples: a Gentry data‑commons on Kubernetes with Jupyter, multiple auth/logging options; one customer spends 14 months to reach production — aim for weeks, not a year. CNCF whitepapers and a platform engineering maturity model back the roadmap and ROI work.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:31Platform engineering
- 11:25Product mindset
- 22:20Minimum viable platform
- 24:01Functional representation of platforms
- 33:04Platform engineering maturity model
- 37:38CNCF resources
- 40:25Outro
related talks
39mPlatform Engineering as a (Community) Service
28mWhat to Expect from Your Application Platform
41mPlatform Engineering for Developers, Architects & the Rest of Us
27mThe Future of Platform Engineering
23mPlatform engineering is all about product
13mBuilding Platforms Through Customer Value: Yes, You Can
25mPlatform Engineering: Evolution or a Fancy Rename?
33mPlatform as a Product - Transforming from Service Delivery into Continuous Operations