Opening Remarks
summary
A personal origin story shows how Docker linking seeded the claim that infrastructure can adapt to applications so developers don’t mutate config; service mesh is framed as the layer that delivers that by handling connectivity, reliability, observability, security. Names dropped: Linkerd, Istio, Envoy, Kubernetes plus VMs and multi‑cluster setups. Specific focuses include performance tradeoffs, monitoring/visibility, automatic mTLS, chaos testing, and growing production and academic use cases; Kong appears as sponsor.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:10Welcome
- 0:35My Experience with ServiceMesh
- 4:50Event Overview
- 5:35Content Overview
- 6:55Category Overview
- 7:55Shoutouts
- 8:35Closing Thoughts
related talks
24mThe Platform Wars, Begun They Have
22mThe Irresistible Rise of Cloud Native: What the Future Means for YOU
14mEverything Worked Before Kubernetes
25mContainers. Microservices. Cloud. Open Source. Fantasy or Reality for Enterprises?
20mTop new CNCF projects to look out for
46mSelf-Organizing Service Infrastructure Based on Docker
44mService Mess to Service Mesh
31mThe Truth About the Service Mesh Data Plane