Vax to K8s: Ticketmaster's Transformation to Cloud Native Devops
summary
Ticketmaster moves 200+ products from a VAX/on‑prem estate into a cloud‑native DevOps model using Docker, Kubernetes (Tectonic/CoreOS), AWS and Terraform, cutting a web platform deploy from 20 minutes to 60 second deploy and recovering full sales within hours after a catastrophic on‑prem outage. The estate still includes 20,000 VMs and legacy Oracle/bare‑metal holdouts, but releases accelerate from weeks to multiple per day, hundreds of engineers train into ops and a measurable drop in manual scaling and downtime appears. 200 products remain in various maturity stages.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 4:02Company scale and architecture
- 10:57The challenges of siloed work
- 16:50The DevOps transformation
- 23:08Moving to cloud native
- 29:52Future steps and conclusion
related talks
34mBringing 1976 into 2016: Ticketmaster’s Public Cloud and Kubernetes Strategy
34mCloud Native Transformation: How Ticketmaster is Changing Culture and Speeding Up
36mDoubling Down on DevOps: Global Transformation at Ticketmaster
59mHow Ticketmaster runs Kubernetes for 80% less without managing VMs
28mDevOps in the Enterprise: A Transformation Journey
28m193 Easy Steps to DevOpsing Your Monolith
24mFrom Lift-and-Shift to K8s: A Two-Phase DevOps Modernization
31mDOES14 - Shakeel Sorathia - Ticketmaster