What are the Challenges faced by the Spotify and How did they Overcome those Challenges using Kubernetes (K8s) ??
Tags: Kubernetes, Spotify, Docker, Cloud, Containers

What are the Challenges faced by the Spotify and How did they Overcome those Challenges using Kubernetes (K8s) ?? Dileepkumar Dec 26, 2020·3 min read

What is Kubernetes ?

Kubernetes is an open-source container-orchestration system for automating computer application deployment, scaling, and management. It was originally designed by Google and is now maintained by the Cloud Native Computing Foundation

Why Kubernetes so special.. 🤔

Automated Scheduling

Self-Healing Capabilities

Automated rollouts & rollback

Horizontal Scaling & Load Balancing

Offers environment consistency for development, testing, and production

Infrastructure is loosely coupled to each component can act as a separate unit

Provides a higher density of resource utilization

Offers enterprise-ready features

Application-centric management

Auto-scalable infrastructure

You can create predictable infrastructure

Spotify is a Swedish audio streaming and media services provider, launched in October 2008. The platform is owned by Spotify AB, a publicly traded company on the New York Stock Exchange since 2018 through its holding company Spotify Technology S.A. based in Luxembourg

Challenges Faced by Spotify

Spotify Launched in 2008, the audio-streaming platform has grown to over 200 million monthly active users across the world. Their intention is to provide a quality services to there customers. They wanted to empower creators and enable a really immersive listening experience for all of the consumers that they have.

In 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 for them 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 for that 💡

They saw the amazing community that had grown up around Kubernetes, and wanted to be part of that.

Kubernetes was more feature-rich than Helios. Plus, they 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”

Conclusion given by Spotify over Kubernetes

A small percentage of their fleet has been migrated to Kubernetes, and some of the things that they heard from their internal teams are that 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 they 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.

Before the companies were working on monolithic architecture. But there are some major problems in monolithic architecture. So all the problems which we are facing in monolithic architecture are solved by Microservices .Kubernetes tools also working on the Microservices architecture .And now almost all companies are using k8s for deployment , scalling and managment

Thanks for Reading….