Back to Catalog
Cloud
azure
Sidecar
Deploy components into a separate process for isolation and encapsulation
Intent & Description
The Sidecar pattern deploys components into a separate process or container to provide isolation and encapsulation. The sidecar runs alongside the main application and provides features like monitoring, logging, configuration, or networking. This keeps the main application focused on business logic while the sidecar handles cross-cutting concerns.
Real-world Use Case
Use when you want to separate cross-cutting concerns from the main application or when you need to add features without modifying the main application code.'
Source
Advantages
- Separation of concerns
- Language and framework independence
- Easy to add and remove features
- Isolated lifecycle management
Disadvantages
- Additional infrastructure complexity
- Resource overhead
- Debugging across processes