Tasked with rebuilding the way we deliver music to DJ's, the Beatport Infrastructure team set out to use Kubernetes to construct scalable compute for executing batch and on-demand encoding workloads in order to level-up our customer's capabilities for playing and mixing dance music.
What would follow is a 5-month journey of building clusters, thrashing with software dependencies, and trudging through erratic performance and scalability issues with the kubernetes API.
How did we decide to use kubernetes? Was it easy to prototype?
Is etcd capable of sustainably servicing 10,000 Jobs an hour? How many Pods can the kubernetes API store? How do you monitor and manage Job failures?
We'll walk you through our lessons learned and talk about our most exciting moments and deflating realizations. Join us we re-tell the story of delivering a correct system to production :)
Leigh is an empathetic speaker and developer with niches in cloud-native systems and security. He has a background in building software to manage infrastructure. Leigh contributes to Kubernetes and Flux and is frequently working on his next software demo. He also co-maintains Ignite... Read More →
John Slivka works on the Infrastructure team at Beatport. Previously, he's worked for IBM Cloud and Oracle Cloud Object Storage as a Software Engineer.
