Get to know Envoy - the modern proxy for cloud-native infrastructure - Baptiste Collard
summary
Envoy runs as a C++ nonblocking proxy with dynamic config without restart and a thread model that multiplexes many sockets per worker; it routes via listeners → network filter chains → the HTTP Connection Manager → clusters populated by XDS/ADS from a control plane. It supports HTTP/3 and all HTTP versions, exposes rich per-connection and per-cluster metrics plus an admin config dump, and calls external authorization (e.g., external auth calling OPA) or transcodes gRPC/JSON. Deployed as sidecars (Kuma) or gateways (Envoy Gateway), it handles dozens of thousands of RPS and is extensible via WASM.
AI-written summary · about
chapters (15)
- 0:00Introduction to Envoy
- 2:13What makes Envoy cloud-native
- 4:44Envoy’s dynamic design
- 7:56Core concepts explained
- 11:33Static configuration overview
- 14:24Dynamic config with control plane
- 15:50Why Envoy for gateways
- 17:37Envoy as service mesh sidecar
- 21:09Performance and adoption
- 22:36Debugging Envoy in practice
- 24:53Metrics and health checks
- 25:38Response flags in access logs
- 27:07Choosing Envoy solutions
- 28:12Next steps and resources
- 29:16Q&A session
