Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Created new term "Sidecar Container" #3353

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions content/en/sidecar-container.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
---
title: Sidecar Container
status: Feedback Appreciated
category: concept
---

The Sidecar Container is an implementation of the sidecar pattern.
An application deployed on a second container will run side by side
and share its lifecycle with a primary application running on a main container.

## Problem it addresses

There are cross-platform situations where it is convenient to group [containers](/container/)
and their lifecycle to deal with scenarios
like logging, monitoring, tracing, but also security, and networking.
Before this approach, logging would typically be implemented in the application code
inside the container.
This can lead to different ways to implement the logic,
depending on the developer or application,
normally resulting in more complex systems to maintain and govern.
For example, updating the logging logic might impact the application in runtime,
hence increasing operational risk.

## How it helps

It enforces the principle of separation of concerns
and provides extending functionality without changing the main application's code,
by using a separated process running on a secondary container.

The sidecar container will share the same resources,
including storage and networking, as the main container.
While doing this, it frees the main container to be focused on functional tasks
iamNoah1 marked this conversation as resolved.
Show resolved Hide resolved
or exposing business capabilities.

For example, when multiple microservices have their sidecar containers
acting as logging agents reading from the same directory,
the main application is writing its logs to.