Grokking Microservices Design Patterns
Vote

0% completed

​

The Architecture of the Sidecar Pattern

One Pod, Two Containers

One of the most distinctive features of the Sidecar Pattern's architecture is its use of containers. The main application and its sidecar run in two separate containers that are scheduled and deployed as a single unit. In Kubernetes that unit is the pod: one pod holds the application container alongside one or more sidecar containers.

The two containers share the pod's network namespace, so the sidecar is reachable from the application at localhost, and they can share mounted volumes. What they do not share is the container image or the process space

.....

.....

.....

Like the course? Get enrolled and start learning!
Debadutta Panda

Debadutta Panda

· 8 months ago

The first paragraph says - The main application and its sidecar are deployed together in the same container,

It should be - in the same pod instead of the same container. It will be separate container always. However, they will be able to share the same resources as long as they are in the same pod.

Tanumoy Majumder

Tanumoy Majumder

· 3 years ago

Lets say we have 3 microservice and we are implementing sidecar for configuration. But configuration for microservice A will be different from microservice B and C.

  1. Side car will be an application which will take care to bring configuraion from git (cloud-config). Please correct me if I am wrong.

  2. Secondly, is this possible to keep separate sidecar application for each microservice?

  3. If for more load microservice B will need vertical scaling. then this Sidecar application will be automatically replicated with application container to new Pods right ?