From Isolated Services to Integrated Ecosystems: Platform Evolution at Deutsche Bahn
summary
Cloud migration starts with selling data centers in 2016 and a hard deadline (no on‑prem DCs by 2021), driving a devops, self‑organized rollout that enables 10,000 developers to manage ~3,000 IT systems. Teams adopt Kubernetes widely but not universally; lift‑and‑shift created quality gaps that spur a platform strategy: six platforms (Developer Experience, Enterprise Integration, Data, AI, IoT, Low/No‑Code), a Backstage‑based developer portal, platform enablement teams, hackathons, multi‑cloud AWS/Azure integrations, and measured adoption improvements to ~80–90% with case‑based ROI estimates.
AI-written summary · about
chapters (7)
- 0:00Introduction and platform concept
- 2:07Need for speed in digitalization
- 7:47Cloud migration and self-organization
- 13:54Developer experience challenges
- 22:00Need for quality and Kubernetes
- 27:20Platform enablement and adoption
- 32:19Need for impact and ecosystem care
related talks
40mLessons Learned Building Developer Platforms
20mPlatform-First Cloud Transformation
26mLessons Learned from 7 years of Running Developer Platforms
43mEngineering Platforms Evolved
11mBuilding Scalable Developer Platforms
26mBuilding Internal Platforms to Enhance Developer Experience
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling