Connectivity Rules Everything Around Us
summary
Software shifts from CPU to network as monoliths become microservices, so connection failures—not code—become the main outage cause. Solution: run tiny Envoy sidecars beside every service (data plane) and push config from a control plane; that enables zero trust, per-service identities, tracing, retries and chaos testing without per-team reimplementation. Kong donates Kuma as an Envoy-based control plane (CNCF sandbox) that supports VMs, multi-zone and multi-mesh topologies to make cross-cloud, edge and in-app connectivity consistent and manageable.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:57Welcome
- 3:45Connectivity
- 6:36Service Connectivity
- 9:52Application Connectivity
- 11:57Connectivity Types
- 12:52InApp Connectivity
- 17:05Service Mesh
- 18:49Edge CrossApp
- 21:13Conclusion
related talks
34mProxies, Gateways, and Meshes: Cloud Connectivity 101 for...
32mAdopting a Modern API Strategy for Hybrid, Multi-Cloud Architectures
01h 31mTutorial: Service Mesh for the Developer Workflow
08mLightning Talk: Move Over API Gateway.... into Your Service Mesh
28mEnvoy Project Intro
17mFully managed Kong Gateway SaaS on Konnect and AWS, with live demo
42mAPI Gateway Pattern & Kong in a Microservices World
29mKong + Yugabyte: Simplifying App Development in a Distributed World