Platform Engineering for Developers, Architects & the Rest of Us
summary
Argues platform engineering must be API-first product work with a three-layer model: application choreography, platform orchestration, and infrastructure orchestration. Demonstrates tools and approaches (Backstage UIs, Terraform/Crossplane/Pulumi/AWS CDK for infra, Dapper-style sidecars, Heroku/Cloud Foundry precedents, and cratics for orchestration) and claims golden bricks (composable services) beat rigid golden paths in practice. Cites developer-experience metrics (DORA/SPACE/DevEx), reports ~50% teams lack success metrics, and shows ownership of flow of value reduces tickets and eases fleet upgrades.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:38tl;dr
- 2:40From k8s to PaaS to, what's next?
- 5:53The "what" of platforms
- 18:14tl;dr
- 19:06(Platform) architecture case studies
- 30:53Key insights
- 38:34Wrapping up
- 40:53Outro
related talks
39mPlatform Engineering as a (Community) Service
45mPlatform Engineering: A Deep Dive Conversation
33mPlatform engineering: Build your own PaaS
15mThe Art of Platform Engineering
42mPlatform Engineering in practice — Why and How to start
21mMake developers fly; Principles for platform engineering
27mThe Future of Platform Engineering
45mPlatform Engineering vs DevOps