Migrating Spotify's runtime to Kubernetes
Spotify recently completed the migration of all services from running on bare-metal hardware to hosts in the cloud on GCP. Spotify is now in the exciting process of journeying from merely cloud hosted to cloud native via migrating the running of services to Kubernetes. James Wen discusses the work involved, lessons learned, and pitfalls encountered in moving services onto Kubernetes.
|Talk Title||Migrating Spotify's runtime to Kubernetes|
|Speakers||James Wen (Spotify)|
|Conf Tag||Build resilient systems at scale|
|Location||New York, New York|
|Date||September 20-22, 2016|
Spotify’s infrastructure is undergoing a drastic transformation from data centers running a large amount of proprietary services to public cloud-hosted, cloud-native services. Two years ago, all of Spotify’s services ran on its own hardware. Today, they are running in hosts on the cloud in Google Cloud Platform, and Spotify is in the process of replacing many of its proprietary systems with open source, cloud-native solutions like Kubernetes. James Wen discusses the specific migration process Spotify followed for moving services and all of runtime to Kubernetes, covering the tightly scoped migration stages that were utilized and the lessons learned at each step. Join in to learn how one company successfully underwent a drastic transition.