Do you really need a platform team?
summary
Argues platform engineering is one scalable path to DevOps outcomes not a replacement for DevOps or SRE, and that an internal developer platform (think managed Kubernetes plus infra and deployment automation) only pays off once “platform investment + integration < devops effort,” so one or two teams usually don’t justify it. Recommends growing a platform from existing repeatable work, treating it as a product with stakeholder engagement, and staffing it with engineers who are devops-first but software-oriented.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:24Platform Engineering
- 1:25Agile Analogy
- 1:54DevOps maturity models
- 2:51SAS architectures
- 3:42PlatformEngineering
- 4:55Platform vs Traditional
- 6:20When
- 8:15What have we learned
- 9:33Dont start from scratch
- 10:04Platform Engineer
related talks
22mDevOps vs Platform Engineering: Navigating the Path Ahead
46mBeyond DevOps: How and Why Companies Converge on Platform Models
45mPlatform Engineering vs DevOps
32mThe Death of DevOps Has Been Greatly Exaggerated, but Platform Engineering Is Here To Stay
39mPlatform Engineering as a (Community) Service
28mDevOps meets reality
38mHow to Empower your DevOps Initiatives with a PlatformOps Approach
56mStill Doing DEVOPS? Platform Engineering Is the Next Big Thing
