API Gateways & Service Mesh: What’s best for us
summary
API gateways handle north-south client-to-service traffic and service meshes handle east-west service-to-service traffic, often both implemented with Envoy sidecars (Istio, Linkerd, Consul) or kernel eBPF (Cilium). Service mesh automates mTLS, tracing and retries across many teams; API gateways (Kong, Emissary/ Ambassador, Gateway API) excel for API-as-product needs: developer portals, billing, WAF, and edge caching to reduce serverless cost. Recommendation: start with an API gateway, add a service mesh when many teams need consistent network security and observability.
AI-written summary · about
chapters (6)
- 0:00Start
- 21:02Is your traffic internal vs external?
- 24:40Observability
- 33:25Deploying a Service Mesh Routing Deployment
- 33:48Deploying API Gateway into a Service Mesh
- 35:41Key takeaways
related talks
39mAPI Gateway to Service Mesh: Navigating a Changing Landscape
30mA Comprehensive Guide to API Gateways, K8s Gateways, and Service Meshes
32mOne API To Rule Them All? What the Gateway API Means For Service Meshes
26mSynchronous Communication Patterns: A journey from ESB to APIs [...]
40mThe Busy Platform Engineers Guide to API Gateways
33mFantastic API Gateways and Where to Find Them
09mK8s API Gateway: Service Mesh Strategies for Scalable Solutions
27mMaster API Gateways: Boost Your Microservices Strategy