Making Sense of the Mesh: A Conceptual Model for Service Mesh Topolog...
summary
Defines service mesh as a control interface over the existing web of services and gives a practical model: three scaling dimensions — control plane, clusters, meshes — with concrete options (run multiple control plane instances, logical control planes, or per-region copies) and tradeoffs. Recommends always use mTLS, describes data-plane forms (sidecar vs node-agent and white‑box gaps like UDP), and explains multi-mesh = identity only federation that isolates config and compute while enabling cross-domain trust.
AI-written summary · about
chapters (13)
- 0:00Making Sense of the Mesh
- 0:35What is a Service Mesh?
- 1:54Microservices
- 2:32N-Tier Architecture
- 6:58Service Management - Doing the Math
- 8:29Anatomy of a Service Mesh
- 10:31Service Mesh Best Practices
- 11:29Three Dimensions
- 12:07Control Plane - Instance Scaling
- 12:52Control Plane - Logical Scaling
- 13:52Multi-Cluster - Scaling Compute
- 18:17Multi-Mesh - Scaling Trust
- 21:01Questions?
related talks
34mWhat a Mesh! From Internet Driven Development to Service Mesh
44mService Mess to Service Mesh
01h 21mFive Cool Things You Can Do with Network Service Mesh
10mLightning Talk: NSM, Network Service Mesh at Scale for Telco Networking
44mStretching the Service Mesh Beyond the Clouds
23mBYO Infrastructure: Who needs to run a control plane, anyway?
42mIstio Multi-Cluster Mesh Expansion BOF
39mBuilding Europe's Cloud Future: NeoNephos' Platform Mesh