Clean-up Your Service Mess with Service Mesh
summary
Demoed a running Kubernetes app using Linkerd tap to inspect live requests (found a planted 404 and traced it to the data API route) and used Istio 85/15 canary routing to split traffic. Architecture uses a sidecar proxy per pod, Prometheus/Grafana for metrics, and an automated CA for TLS. Observability surfaces a quakes endpoint averaging ~5s latency across replicas; service mesh policies enable circuit breaking, traffic mirroring and tracing without changing application code.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:33About Brian Redmond
- 1:29Microservices
- 2:13Demo
- 3:03Example
- 6:14What is Service Mesh
- 7:20You need more observability
- 7:58Intelligent routing
- 8:39Security
- 9:17Shared Libraries
- 10:01Service Mesh
- 11:16LinkD Architecture
- 13:00Observability
- 13:46Intelligent Load Balancing
- 15:13Encryption
- 15:54Circuit Breaker
- 16:59Other Benefits
- 17:56Do You Need a Service Mesh
- 19:17Service Mesh Technologies
- 19:53Service Proxy
- 20:31API Gateway
- 21:04Console Connector
- 21:29Demos
- 22:02Kubernetes
- 24:27Dashboards
- 27:15Control Plane
- 29:40Summary
related talks
29mDebugging an app with a service mesh
37mThe Service Mesh Wars: A New Hope for Kubernetes
47mService mesh options with Istio, Linkerd, and/or Consul
26mNavigating the Service Mesh Landscape - Paul Bouwer, Microsoft
44mService Mess to Service Mesh
26mChoosing a Service Mesh
43mService Mesh and the future of networking
38mPanel Discussion: Ask Us Anything: Microservices and Service Mesh