Pattern 43 / INFRA
Use this when adding cross-cutting behavior without modifying the main app.
Sidecar Pattern fits when adding cross-cutting behavior without modifying the main app. Mechanism: run a helper process next to the workload in the same pod/container group. Use it for logging agents, proxies, config reloaders, secret sync, and monitoring collectors. The toll: resource overhead and lifecycle coupling with the main service.
Logging agents, proxies, config reloaders, secret sync, and monitoring collectors.
Log shipper sidecar tails app logs and sends them to storage.
Describe the pressure first, then the mechanism, then the cost. That keeps the design grounded.
Same pressure family