Synchronous Communication Patterns: A journey from ESB to APIs [...]
summary
Claim: moving from a centralized ESB to an API gateway and then to a service mesh reduces firewall and gateway churn for service-to-service calls and smooths VM→Kubernetes migration. Implementation uses Kong API Gateway for partner exposure and Kuma service mesh (with Envoy proxy) for in-cluster routing; a hybrid control plane spans VM and K8s zones. Prototype installs without blockers and routes traffic correctly, while transversal security and reuse of legacy ESB connectors remain unresolved.
AI-written summary · about
chapters (7)
- 0:00Start
- 6:43The journey
- 9:41New architecture
- 11:19Kong project
- 13:48API to API communication
- 15:48Kuma prototype
- 20:00Key elements
related talks
39mAPI Gateway to Service Mesh: Navigating a Changing Landscape
38mAPI Gateways & Service Mesh: What’s best for us
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
22mConnectivity rules everything around us
09mK8s API Gateway: Service Mesh Strategies for Scalable Solutions
40mThe Busy Platform Engineers Guide to API Gateways
55mAPI Gateways with Kong