Bringing 1976 into 2016: Ticketmaster’s Public Cloud and Kubernetes Strategy
summary
Ticketmaster describes migrating four decades of systems — 21 full ticketing engines, 250 products, 22,000 VMs and 15,000 network endpoints supporting $25B in commerce for 530M fans — into public cloud and Kubernetes. Teams use Docker, Terraform, CoreOS/Tectonic, Calico, Prometheus and Linkerd; a POC runs OpenTSDB at ~500k metrics/sec and uses Kubernetes pod health checks to auto‑recover. A product inventory plus a 40‑capability tech maturity model drive which apps are replatformed or retired.
AI-written summary · about
chapters (35)
- 0:00Intro
- 0:48Justin Dean
- 1:34Why Kubernetes
- 2:37History of Ticketmaster
- 3:58What does Ticketmaster do
- 4:35Our company mission
- 5:15Speeds and feeds
- 6:58Competitive landscape
- 8:07Tech complexity
- 11:55Public company pressures
- 12:41Simplifying the platform
- 13:51Simplifying everything
- 14:17Let the makers make right
- 14:56Make a business case
- 15:31Ticketmasters journey
- 16:11Lean transformation
- 17:09DevOps
- 17:59Public Cloud
- 19:00Kubernetes
- 19:47Public Lab
- 21:59Tech maturity model
- 23:44Cloud readiness
- 24:14Cloud enablement
- 24:57The CT method
- 26:00Using Kubernetes
- 26:29POC II
- 27:24Hosts
- 28:13Milestones
- 29:13Core OS
- 29:31PR Review
- 29:58Kelsey Hightower
- 30:29CoreWes
- 30:46Architecture
- 32:18Kubernetes Community
- 33:33Afterparty
related talks
34mCloud Native Transformation: How Ticketmaster is Changing Culture and Speeding Up
44mVax to K8s: Ticketmaster's Transformation to Cloud Native Devops
59mHow Ticketmaster runs Kubernetes for 80% less without managing VMs
14mKeynote: Lessons and Rhythms from the Hybrid Cloud
24mFrom Lift-and-Shift to K8s: A Two-Phase DevOps Modernization
53mThe Thorns of Containerized Applications and Microservices
33mNavigating the Seas of Transformation: Migrating from EC2 to Kubernetes
29mFrom EC2 to Kubernetes Takeaways from a Brownfield Migration