← Back to microservices patterns mapinfra
Microservices Pattern
Sidecar Pattern
Run a helper container beside the app to handle cross-cutting infrastructure concerns.
Detailed Description
Sidecars move infrastructure behavior out of application code. The main service stays focused on business behavior.
This is common for proxies, log collectors, telemetry agents, and certificate rotation.
Visual Diagram
Kubernetes Pod ┌─────────────────────────────────┐ │ Pod │ │ ┌────────────┐ ┌─────────────┐ │ │ │ Main App │ │ Sidecar │ │ │ │ :8080 │ │ Envoy Proxy│ │ │ │ │ │ Log Agent │ │ │ └────────────┘ └─────────────┘ │ │ shared network + storage │ └─────────────────────────────────┘
Tradeoffs
Pros
Language agnostic, no app-code changes
Cons
Extra resources and operational moving parts
Examples: Istio Envoy sidecar, Datadog agent, Fluentd
Comments
Sign in to leave a comment. Your name and photo come from Google; nothing else is shared.
Loading comments...
All courses
24 courses in 5 subjects
AI
System Design
Backend
- GraphQL8 modules · 69 lessons planned
- Core Python13 modules · 75 lessons planned
- FastAPI5 sections · 20 lessons
- Node.js14 modules · 206 lessons planned
- Node.js Performance7 chapters · 36 topics
- Event Loop Lifecycle6 phases · 3 scenarios
- Docker & Containerization11 modules · 144 lessons planned
- AWS for Developers14 modules · 219 lessons planned
- CI/CD & DevOps Automation10 modules · 134 lessons planned
Frontend
Fundamentals
On this page
0 sections