Case Study On Kubernetes : BOSE

Before jump to case study Let’s first understand what Kubernetes is ?

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 you need Kubernetes and what it can do

Containers are a good way to bundle and run your applications. In a production environment, you need to manage the containers that run the applications and ensure that there is no downtime. For example, if a container goes down, another container needs to start. Wouldn’t it be easier if this behavior was handled by a system?

That’s how Kubernetes comes to the rescue! Kubernetes provides you with a framework to run distributed systems resiliently. It takes care of scaling and failover for your application, provides deployment patterns, and more. For example, Kubernetes can easily manage a canary deployment for your system.

For more information :

Nowadays most of the companies making use of Kubernetes for their beneficiary.

In this blog we are going see how BOSE Corporation(one of the giant company) making use of Kubernetes

Before this Lets little bit know about Bose Corporation:

Bose Corporation is an American manufacturing company that used to sells audio equipment. The company was established by Amar Bose in 1964 and is based in Framingham, Massachusetts.

Let’s See How Bose is making use of Kubernetes:

Bose: Supporting Rapid Development for Millions of IoT Products With Kubernetes

A household name in high-quality audio equipment, Bose has offered connected products for more than five years, and as that demand grew, the infrastructure had to change to support it. Bose started looking into microservices architecture.

“We needed to provide a mechanism for developers to rapidly prototype and deploy services all the way to production pretty fast.

- Lead Cloud Engineer Josh West.

From the beginning, the team knew it wanted a microservices architecture. After evaluating and prototyping a couple of orchestration solutions, the team decided to adopt Kubernetes for its scaled IoT Platform-as-a-Service running on AWS.

Impact:

With about 100 engineers onboarded, the platform is now enabling 30,000 non-production deployments across dozens of microservices per year. In 2018, there were 1250+ production deployments. Just one production cluster holds 1,800 namespaces and 340 worker nodes.

That’s it.

For more information check out the following:

Happy Learning!