Your platform is not an island: building a platform for your ecosystem
summary
Built a Kubernetes platform alongside an existing Cloud Foundry estate, with automated provisioning of per-team cloud accounts and a shared responsibility model; onboarding shifts to GitOps pull requests and declarative config so teams declare desired state while the platform orchestrates. The platform targets the middle 80% of use cases, reduces handoffs (from four teams to three in one flow), and improves developer onboarding and transparency — it succeeds for many teams but remains hybrid and imperfect for edge cases.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:37Your organization is an ecosystem
- 2:47Your ecosystem is not just your people
- 4:16Silos
- 5:54Complexity
- 6:07Maturity
- 6:25The reality
- 8:09Why build platforms
- 9:56Developer experience
- 10:41Case study
- 10:59Before public cloud
- 11:53Public cloud
- 13:28App experts
- 14:20Full circle
- 15:29Developer choice
- 18:35Challenges
- 19:45Golden path
- 21:05Meeting the people
- 21:34Offering an option
- 22:03Dynamic configuration generation
- 24:01Platform and capability providers
- 26:05How to apply this to your enterprise
- 27:52Smoothing the process
- 28:19Outro
related talks
27mOvercoming Obstacles and Building Self-service Platforms for Application Teams
24mA Cloud Native Foundation For Developer/Application Platforms
23mHow the Cloud Foundry Community Can Help Platform Engineering
37mPlatform Reality Has a Surprising Amount of Detail
24mFrom Kubernetes to PaaS to Developer Control Planes
14mPlatforms aren't tools, they are experiences
06mLightning Talk: Blueprints of Innovation: Engineering Paved Paths for a User...
29mThe Key to Faster Delivery: Collaborative Platform Strategies