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.
James Wen is a site reliability engineer at Spotify, where he’s currently focused on revamping Spotify’s infrastructure and adopting Kubernetes. Previously, James was the team lead (anchor) of the Cloud Foundry buildpacks team at Pivotal and a core contributor and maintainer of Bundler. James has spoken about buildpacks at Cloud Foundry Summit Europe and Spotify’s infrastructure journey and migrations at QCon New York, KubeCon Europe, and DevfestDC. He loves climbing, whether it’s on gorgeous Fontainebleau slopers or nasty plastic crimps.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org