Service Mesh: Service-to-Service Traffic

Sidecars, control vs data plane, mTLS identity, retries and circuit breaking in the mesh, traffic splitting, ambient/sidecarless — and when not to adopt one.

About 75 minutes · 15 exam questions · 9 interview questions · 2 code labs

What you will learn

  1. What a service mesh is (and why it exists)
  2. Control plane vs data plane (how a request actually flows)
  3. mTLS and workload identity
  4. Timeouts, retries and circuit breaking in the mesh
  5. Traffic splitting, header routing and mirroring
  6. Observability: what the mesh gives you and what it can’t
  7. Sidecar vs sidecarless: ambient, eBPF and proxyless gRPC
  8. Mesh failure modes you will meet in production
  9. When NOT to adopt a mesh, anti-patterns, and choosing one

Previous: Reverse Proxy, Forward Proxy, API Gateway & BFF · Next: Load Balancing: L4/L7, Algorithms, Consistent Hashing