Solving the Service Mesh Adopter's Dilemma
summary
A management plane called Meshery provisions and benchmarks service meshes and sample apps it runs as a Docker Compose server with adapters for six meshes and talks to Kubernetes and Prometheus Grafana it runs comparative load tests that produce p50 p75 p99 and even p99.9 latencies and the project reports being ~1,000 tests into a Service Mesh Performance spec Meshery also vets mesh configs against best practices and shows whether each mesh’s control plane and sidecar model actually works in a given environment
AI-written summary · about
chapters (9)
- 0:00Start
- 10:18Observability
- 12:13Traffic Control
- 14:29Why use a Service Mesh?
- 17:57Stacking up Service Mesh
- 18:49Third step in Cloud Native journey
- 19:59Decoupling at Layer 5
- 28:38Service mesh abstractions to the rescue 5
- 34:40Configuration Best Practices
related talks
53mDo you need a Service Mesh?
28mService Meshes: At What Cost?
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
30mA Developer’s Introduction to Service Mesh
43mWTF Do We Need a Service Mesh?
56mService Meshes - Powering the next wave of microservice architectures
26mAn Introduction to Service Mesh in Action
39mDo you need a Service Mesh?
