Keynote: Lessons and Rhythms from the Hybrid Cloud
summary
Ticketmaster adopts a hybrid cloud: a public cloud platform for bursty loads and developer velocity and an on‑prem Kubernetes cluster for kubernetes on-prem cluster and always‑on, dense workloads like search, Kafka and data mining that were far cheaper on Prem. Concert drops cause 5–30 minute spikes of 20×–250× baseline traffic so public cloud elasticity powers Verified Fan, while stadium scanners require better‑than‑internet SLAs. Hybrid brings Direct Connect/VPN latency, doubled security/governance complexity, and a need for automation, unified policies, asset tracking and cross‑platform monitoring.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:44Why do I have a guitar
- 4:08Why do I have a hybrid cloud
- 5:52Why do I have a public cloud
- 7:00Not all services fit
- 9:27Lessons from Hybrid Cloud
related talks
34mBringing 1976 into 2016: Ticketmaster’s Public Cloud and Kubernetes Strategy
34mCloud Native Transformation: How Ticketmaster is Changing Culture and Speeding Up
44mVax to K8s: Ticketmaster's Transformation to Cloud Native Devops
19mKeynote: Building Bridges: Cloud Native and High Performance Computing
05mSponsored Keynote: Kubernetes Everywhere
14mKeynote: The Big Leap: Conquering the Legacy System and Building a Scalable Cloud...
22mHybrid cloud, extend your on-premises infrastructre?
35mHybrid Cloud Powered by Kubernetes [I]