Make developers fly; Principles for platform engineering
summary
Platform engineering claims to cut developer cognitive load by treating platforms as products, using team topologies and four operational models: centralized provisioning, platform-enabled golden paths, embedded DevOps, and decentralized DevOps leading to a decentralized developer platform. Practical implementation uses versioned, customizable templates and inner-source workflows; AWS maps this to concrete tools like AWS Proton with versioned environment templates and service templates that are self-serve, transparent, and contributable via git.
AI-written summary · about
chapters (12)
- 0:00Platform engineering vision
- 1:04Why platform engineering needed
- 3:34Defining platform engineering
- 5:20Team topology and roles
- 7:10Effective platform traits
- 8:37Platform design beyond tech
- 10:04Four developer platform models
- 12:54VDUX principles
- 16:26Cloud’s role in platforms
- 18:17Platform interface mapping
- 19:18AWS Proton automation
- 21:07Q&A
related talks
41mPlatform Engineering for Developers, Architects & the Rest of Us
27mThe Future of Platform Engineering
45mThe Future of Platform Engineering
39mPlatform Engineering as a (Community) Service
15mThe Art of Platform Engineering
45mPlatform Engineering vs DevOps
42mPlatform Engineering in practice — Why and How to start
25mPlatform Engineering: Evolution or a Fancy Rename?
