The Future of Platform Engineering
summary
Claims that platforms succeed when they provide concrete blueprints and ownership patterns rather than vague guidance and promise. Uses AWS primitives: an account vending machine, managed clusters, and AWS CDK constructs as deployable patterns; automates with infrastructure as code and APIs; pushes a hybrid ownership model (centralized blueprints, decentralized innovation) and measures success by reduced TCO, faster onboarding, and fewer platform-team bottlenecks. Advocates a golden path of opinionated defaults and a floating platform that continuously adapts to its cloud base.
AI-written summary · about
chapters (9)
- 0:00intro
- 0:14bold statement
- 1:03defining platforms and their importance
- 2:12the role of standards in innovation
- 5:30key characteristics of successful platforms
- 12:50decentralized vs centralized platform approaches
- 15:41ownership patterns in platform engineering
- 23:34building evolutionary platforms
- 26:25conclusion and final thoughts
related talks
45mThe Future of Platform Engineering
39mPlatform Engineering as a (Community) Service
41mPlatform Engineering for Developers, Architects & the Rest of Us
21mMake developers fly; Principles for platform engineering
15mThe Art of Platform Engineering
33mPlatform engineering: Build your own PaaS
33mThe Platform Engineering Journey
41mPlatform as a Product