Why this matters
- At StreamHub scale (40+ microservices), implementing retries, timeouts, and mutual TLS in every language and framework is unmaintainable.
- Istio or Linkerd sidecars give platform engineers uniform observability and security without asking each team to reinvent the wheel.
- Canary deployments and fault injection become configuration changes, not code changes.
Service mesh layers
- Data plane — Envoy sidecar proxies on every pod; handle actual traffic routing, encryption, metrics.
- Control plane — Istiod configures all sidecars; distributes certificates, routing rules, policies.
- mTLS — automatic mutual TLS between services; no application code changes required.
- Traffic management — weighted routing, retries, timeouts, circuit breakers via VirtualService.
- Observability — automatic trace propagation, request metrics, access logs from every hop.
Sidecar architecture
Istio service mesh on EKS
Traffic never flows directly from Service A to Service B. Both pods communicate through their local Envoy sidecars, which the control plane configures.
apiVersion: apps/v1
kind: Deployment
metadata:
name: streamhub-catalog
spec:
template:
metadata:
annotations:
sidecar.istio.io/inject: "true"
spec:
containers:
- name: catalog
image: registry.streamhub.io/catalog:3.1.0
ports:
- containerPort: 8080
# Envoy sidecar injected automatically by Istio
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 4 sections
- mTLS without code changes
- Traffic management and canary deploys
- Circuit breaking
- When not to use a mesh
Test yourself
Answer these before moving on — recall is what makes it stick.