Event-Driven Design: The Core Principle Behind Kubernetes Architecture

Sat, 24 Jan 2026 15:56:13 +0000

Note: This is a handwritten blog. In this blog, we should explore the event where the architecture of Kubernetes is discussed. It will be very short.

As you know, Kubernetes follows an event-driven architecture. The Kubernetes control plane heavily consumes events. But most distributed systems follow RPCs to trigger behavior, but Kubernetes does not.

Reason behind why Kubernetes is not built using RPCs:

Tight coupling: RPCs create strong dependencies between components. In Kubernetes, control plane components must remain loosely coupled to evolve and scale independently.
Poor failure handling: RPCs expect the caller and callee to be alive at the same time. In a distributed system like Kubernetes, transient failures are common and break this assumption.
Scalability limits: Synchronous RPC calls don’t scale well when thousands of objects and controllers are involved. They can easily become bottlenecks.

Let’s understand this scenario with one simple example. When you create a Deployment, the following happens:

What is the most powerful feature of Kubernetes ?

Fri, 16 Jan 2026 07:26:14 +0000

Note: This is hand written blog. In this blog, we gonna discuss about that feature which become one of the main reason behind the success of Kubernetes.

Let’s start with a bit of history. Before Docker and Kubernetes, Google had been running an containers and orchestration system called Borg internally for so many years. Docker changed the way software is built. So, Googlers definitely had the confidence that something called Kubernetes was going to create a lot of impact in the upcoming decade and I would say google was right.

Controller on Anish Bista

Event-Driven Design: The Core Principle Behind Kubernetes Architecture

What is the most powerful feature of Kubernetes ?