Implementing Sidecars Microservice Pattern using Envoy Proxy
summary
Hands-on demo builds two services (product in Python Flask, inventory in Java Spring) deployed with Envoy Proxy as per-container sidecars, configured via Docker Compose and YAML clusters; authentication uses Keycloak JWT checks and a custom Lua filter for request logging. Requests route product→product-sidecar→inventory-sidecar, the demo shows token rejection and expected 500/404 behavior, and covers admin metrics, tradeoffs (extra latency and resource overhead) and when to prefer sidecars.
AI-written summary · about
chapters (16)
- 0:00Intro
- 2:14Agenda
- 4:17Sidecars Microservice
- 7:43Sidecars Implementation
- 10:40Sidecars Key Characteristics
- 13:37Sidecars vs API Gateway
- 17:03Sidecars Architecture
- 19:49Sidecars Code
- 27:00Authentication
- 29:20Clusters
- 35:33Upstream Cluster
- 37:53Docker File
- 41:49Service to Service Authorization
- 46:23Demo
- 51:50Benefits and tradeoffs
- 55:10Dynamic Service Discovery
related talks
50mService Mesh and Sidecars with Istio and Envoy
58mService Mesh and Sidecars with Istio and Envoy
28mService Mesh and Sidecars with Istio and Envoy
47mService Mesh and Sidecars with Istio and Envoy
32mWhy Sidecars? Moving the Stack out of the Monolith
28mEnvoy at Square
30mAdding Sidecars to Cloud Foundry - Gabriel Rosenhouse & Angela Chin
49mMaking Microservices Micro with Istio Service Mesh
