Istio - The Weather Company's Journey
summary
The Weather Company describes incrementally replacing homegrown routing with Istio to gain fleet visibility and control: they handle 24 Billion requests per day, manage ~40 backend APIs, and route 240 load‑balanced services. They deploy Kubernetes edge gateways and use 40 service entries to bring VPC backends into the mesh, push metrics to Prometheus and visualize with Netflix Vizceral, see 60% cached responses reducing origin load, cut manual troubleshooting that once took eight hours, and run production pilots on Istio 0.7 while validating Istio 0.8 features.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:15Background
- 0:39API Weather Calm
- 1:07Weather Calm microservices
- 1:39Android iOS integrations
- 1:56Weather API
- 2:20Main Functions
- 2:47Sun Platform
- 4:22Routing
- 6:10Routing Platform
- 7:19Improvements
- 8:33Issues
- 10:27Tooling
- 10:59Why Istio
- 12:18Istio Platform
- 14:33Current Weather API
- 14:52Service Entries
- 16:30Intercept
- 17:53Monitoring
- 18:09Isolation
- 18:35Dashboards
- 20:02Endpoints
- 20:40Vistio
- 20:59Where are we today
- 22:05Advice for users
- 23:07Recap
- 24:15Questions
related talks
24mIstio in Production: Expected Value, Results, and Effort
36mIstio: Real world scenarios
19mIstio, we have a problem! Understanding and fixing bugs with a service-mesh
08mIstio Adoption Journeys
36mIstio, we have a problem! Understanding and fixing bugs with a service-mesh
30mApp Connect's Journey to Istio
10mLightning Talk: Optimise Your Mesh With Istio Sidecar
13mLightning Talk: Troubleshooting Istio Ambient With Kiali 2.0