Balancing Service Centralisation &Team Autonomy in DevOps Organisation Anna McDougall, Andreas Prang
summary
75% of teams pick a centralized platform so Maps becomes the chosen solution; Maps 1 takes ~4 weeks to provision an environment, Maps 2.0 reduces that to under a day and ships weekly feature releases with automated staging rollouts. The platform runs Kubernetes with Flux v2, offers a Docker-based Maps CLI for operators and frontends, supports per-PR Phoenix environments, uses Spacelift for IaC pipelines, and still allows admin rights while planning tighter permissions and better finops.
AI-written summary · about
chapters (15)
- 0:00Introduction and speakers
- 0:42About National Media and Tech
- 2:50Background and cloud migration
- 4:17Centralization vs autonomy debate
- 5:42Key challenges identified
- 7:29Introducing MAPS platform
- 8:53Platform goals and solutions
- 11:02MAPS 1.0 limitations
- 12:27Building MAPS 2.0
- 14:20Scaling MAPS 2.0 success
- 15:27Empowering different personas
- 19:23Challenges and resistance
- 21:09Expanding to One Cloud Platform
- 22:32Key lessons learned
- 23:59Q&A session
related talks
36mPractical Cloud Native: What Works, What Doesn't
12mKeynote: What It's Like to Bring DevOps to a Software Factory in Central America
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
37mAchieving High Performance with an Internal Developer Platform
15mSpace, the final frontier
41mRediscovering DevOps' Heartbeat: A Journey with Cloud Development Environments
46mBeyond DevOps: How and Why Companies Converge on Platform Models
40mScaling Startup for Success: Building modern Architectures and Developer Acceleration