Warden — Why We Need Our Own Service Mesh?
summary
Describes why Ozon built their own service mesh called Warden instead of using existing solutions like Nginx or Istio; it focuses on problems of service discovery and load balancing in interservice communication and explains Ozon’s custom approach to implementing discovery and balancing (client-side and/or control-plane patterns) within their infrastructure.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:12Service mesh evolution
- 8:55Modern mesh challenges
- 10:41Discovery in Warden
- 11:03Load balancing algorithms
- 16:20Algorithm experiments
- 18:23Canary deployments
- 22:35Sap-sitting problem
- 26:07Warden feature expansion
- 27:54Multi-DC traffic localization
- 31:26Warden future and federation
- 34:59Summary
- 35:43Q&A
related talks
24mOxia - A Horizontally Scalable Alternative to Apache Zookeeper
37mThe Service Mesh Wars: A New Hope for Kubernetes
27mTowards Modern Development of Cloud Applications
32mService Mesh - Beyond the Hype
41mService Mesh beyond single clusters
59mMonolith, Microservices or Both: Modern application development using Service Weaver
45mService Mesh Big Survey
48mProxies, Gateways, and Service Mesh. Why Are Words so Confusing?