Platform Engineering as a (Community) Service
summary
Argues that successful platforms combine tech and human support with executive buy in and real cloud experience, not just Kubernetes hype; recommends platform contract to split responsibilities, self-service automation (avoid five separate Jira tickets), curated stack choices and templated CI/CD. Gives concrete builds: a functioning CockroachDB operator that lets teams create global DBs, an OpenShift case where blocked cloud access forced bad architectures, and clients who rebuilt logging because platform observability failed; outcome hinges on reliability, flexibility and measurable boundaries.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:48Our observation
- 1:30Agenda
- 1:56What is platform engineering?
- 5:24Target communities
- 8:56Characteristics of a successful platform experience
- 18:31How to "platform engineer" well
- 37:55Conclusion
related talks
41mPlatform Engineering for Developers, Architects & the Rest of Us
33mPlatform engineering: Build your own PaaS
15mThe Art of Platform Engineering
27mBeyond Platform Engineering
42mPlatform Engineering in practice — Why and How to start
27mThe Future of Platform Engineering
15mPlatform Engineering - About Tools...
32mPlatform Engineering Is Not About Tech