Kubernetes

Distributed system design patterns

How to organize multi-container application Sidecar pattern Let’s start with a single node. It’s a common practice to seperate concerns also on the container levels. One container could act as a static content server, and the other could perform computations. They both exist on the same node and both have access to the same resources - although you may allocate different CPU and memory consumption. Another popular scenario is to have a seperate container that handles logs of the other container as both share the same disk volume.

Continue reading