Connectivity rules everything around us
summary
Connectivity is the backbone as applications fragment: edge APIs need an edge gateway as ingress/egress while internal teams use internal gateways, and intra-application calls use a service sidecar per instance to handle retries, timeouts, security and observability. The stack shown uses Envoy as the data-plane proxy and Kuma as the control plane (donated to CNCF), with Kong integrating gateway and mesh to run across VMs and Kubernetes, multi-zone and hybrid clouds, enabling zero-trust policies and L4/L7 visibility.
AI-written summary · about
chapters (5)
related talks
26mSynchronous Communication Patterns: A journey from ESB to APIs [...]
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
54mCloud Native Communication: Using Ambassador and Consul Connect with Java Apps
32mOne API To Rule Them All? What the Gateway API Means For Service Meshes
40mReimagining Application Networking and Security
29mThe rise of Layer 7, microservices, and the proxy war...