Kubernetes !! How Spotify is benefiting from it …..

Anirudh Bambhania
4 min readDec 26, 2020

Kubernetes also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon 15 years of experience of running production workloads at Google, combined with best-of-breed ideas and practices from the community.

What’s so cool about Kubernetes and why it is gaining popularity

Run K8s Anywhere

  • Kubernetes is open source giving you the freedom to take advantage of on-premises, hybrid, or public cloud infrastructure, letting you effortlessly move workloads to where it matters to you.

Never Outgrow

  • Whether testing locally or running a global enterprise, Kubernetes flexibility grows with you to deliver your applications consistently and easily no matter how complex your need is.

Planet Scale

  • Designed on the same principles that allows Google to run billions of containers a week, Kubernetes can scale without increasing your ops team.
  • The global application container market is expected to grow from USD 1.2 billion in 2018 to USD 4.98 billion by 2023, at a CAGR of 32.9% during the forecast period. This growth is expected to be fueled by the increasing number of container orchestration services and container security services deployed in enterprises globally

How Spotify is benefiting from Kubernetes

Challenge

  • Launched in 2008, the audio-streaming platform has grown to over 200 million monthly active users across the world.An early adopter of microservices and Docker, Spotify had containerized microservices running across its fleet of VMs with a homegrown container orchestration system called Helios. By late 2017, it became clear that having a small team working on the features was just not as efficient as adopting something that was supported by a much bigger community.

Solution

  • Kubernetes was more feature-rich than Helios. Plus, “we wanted to benefit from added velocity and reduced cost, and also align with the rest of the industry on best practices and tools.” At the same time, the team wanted to contribute its expertise and influence in the flourishing Kubernetes community. The migration, which would happen in parallel with Helios running, could go smoothly because “Kubernetes fit very nicely as a complement and now as a replacement to Helios

Benefits

  • The team spent much of 2018 addressing the core technology issues required for a migration, which started late that year and is a big focus for 2019. they have less of a need to focus on manual capacity provisioning and more time to focus on delivering features for Spotify The biggest service currently running on Kubernetes takes about 10 million requests per second as an aggregate service and benefits greatly from autoscaling,Before, teams would have to wait for an hour to create a new service and get an operational host to run it in production, but with Kubernetes, they can do that on the order of seconds and minutes.” In addition, with Kubernetes’s bin-packing and multi-tenancy capabilities, CPU utilization has improved on average two- to threefold.
  • All four of the top-level metrics that Spotify looks at — lead time, deployment frequency, time to resolution, and operational load — “there is impact that Kubernetes is having.”
  • One success story that’s come out of the early days of Kubernetes is a tool called Slingshot that a Spotify team built on Kubernetes. “With a pull request, it creates a temporary staging environment that self destructs after 24 hours,” “It’s all facilitated by Kubernetes, so that’s kind of an exciting example of how, once the technology is out there and ready to use, people start to build on top of it and craft their own solutions, even beyond what we might have envisioned as the initial purpose of it.”
  • Spotify has also started to use gRPC and Envoy, replacing existing homegrown solutions, just as it had with Kubernetes.

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

Thank You

--

--