Skip to content

Commit

Permalink
created new sidecar-container.md
Browse files Browse the repository at this point in the history
Signed-off-by: Fernando Harris <[email protected]>
  • Loading branch information
fharris committed Jun 3, 2024
1 parent 39b8da4 commit 8c7d678
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/en/sidecar-container.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ There are scenarios where it is convenient to group [containers](/container/) to

## How it helps

The sidecar terms come after the representation of a classic motorcycle with its attached sidecar. In this metaphor, the bike represents the main container and the sidecar the secondary container. This heterogeneous approach consists of using a separated and isolated process running on a secondary container to address problems that aren't unique to a single application but rather to the entire platform where the application is running. It enforces Separation of Concerns, centralised configuration and governance best practices. Besides its flexibility, it presents other advantages such as extending functionality without changing the main application's code, using different languages deployed on different runtimes, and sharing local resources between the core and the secondary applications.
The sidecar terms come after the representation of a classic motorcycle with its attached sidecar. In this metaphor, the bike represents the main container and the sidecar the secondary container. This heterogeneous approach consists of using a separated and isolated process running on a secondary container to address problems that aren't unique to a single application but rather to the entire platform where the application is running. It enforces Separation of Concerns, centralised configuration and governance best practices. Besides its flexibility, it presents other advantages such as extending functionality without changing the main application's code, using different languages deployed on different runtimes, and sharing local resources between the core and the secondary applications.

When applied to Kubernetes deployments, this approach will create a relationship of 1 pod to many containers and implies that operational actions used to the pod, such as creation, scaling, and termination, will be equally applied to all containers inside.

0 comments on commit 8c7d678

Please sign in to comment.