It's a Multi-Mesh World
summary
Service meshes proliferate and three open specs aim to tame them: SMI for a lowest-common-denominator API, SMPS for repeatable performance benchmarks, and Hamlet for exchanging service catalogs. Meshery is the canonical SMPS implementation and automates deployment of eight different meshes, runs a sample app, generates load, measures CPU/memory/latency/throughput, and asserts SMI conformance so teams can compare overhead across 20+ meshes, evaluate WebAssembly filters, and choose sidecar or node-agent models.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:43What is a Service Mesh?
- 3:35Service Mesh Functionality
- 4:48Decoupling at Layer 5
- 6:59Strengths of Service Mesh Implementations
- 16:11Service mesh abstractions to the rescue
- 18:20Service Mesh Performance
- 20:08Comparing types of functions
- 20:35Comparing types of Data Plane filtering
- 25:57Service Mesh Interface (SMI) Conformance
related talks
30mTo Mesh or not to Mesh
20mNetwork Service Mesh
33mCNCF TAG Network and Service Mesh Working Group Deep-Dive
47mService-Mesh: an In-Depth View of Technologies and Reasons for Adoption
47mService mesh options with Istio, Linkerd, and/or Consul
20mNetwork Service Mesh
43mService Mesh and the future of networking
31mThe Future of Service Meshes: Sidecarless or eBPF?
