Platform Engineering - a 1 mln $ worth change
summary
Claims a >$1,000,000 yearly saving — about 20% of a $5M IT budget — backed by a concrete headcount-and-hours example (10 app teams × 6 devs × $50/hr × one week per release → $1,440,000/year). Builds an internal developer platform with automated provisioning: kubernetes namespaces and CI/CD pipelines, demo services prewired to databases, logging, tracing and messaging, plus an internal developer portal or API layer. Orchestration scripts create resources in minutes and the case calculation shows the savings are realizable.
AI-written summary · about
chapters (9)
- 0:00intro
- 0:14saving big on it costs
- 1:00understanding platform engineering
- 1:57organizational changes for platform engineering
- 3:51approaching platform engineering
- 6:10real-world example of platform engineering
- 10:45technological perspective of platform engineering
- 12:43proving the savings
- 14:44conclusion and call to action
related talks
25mFrom Ops to Impact: Scaling Engineering Velocity
42mPlatform Engineering in practice — Why and How to start
25mPlatform Engineering: Evolution or a Fancy Rename?
29mMaking the Business Case for DevOps
41mPlatform Engineering for Developers, Architects & the Rest of Us
44mPlatform Engineering 101: Building Internal Developer Platforms
51mPlatform Engineering for Private Cloud
56mStill Doing DEVOPS? Platform Engineering Is the Next Big Thing