How Niantic Switched Pokémon GO to Use Envoy

Discover how Niantic, creators of Pokémon GO, transitioned from NGINX to Envoy to handle millions of concurrent players worldwide. Learn about the challenges faced, the implementation of a service mesh, and the extension of Envoy to support proprietary protocols. Explore the scaling process using xDS, load testing strategies, and the final launch consolidation. Gain insights into Niantic's mission, their Real World Platform, and the reasons behind choosing Envoy. Delve into deployment overviews, production migration steps, and lessons learned from extending Envoy for Niantic's frontend.

Intro
Niantic Mission
Niantic Real World Platform
Issues to solve
Service-gateway overview
Service mesh implementation Why not istio and others?
Service-gateway Next steps
Deployment overview
Goals
Scaling is a 4 steps process For example, scaling up
XDS to the rescue!
Current deployment
(very) High level plan
Preparing production environment
IP Deny List
Production migration - day 1+
Envoy live in Production
503 UH: UH (no healthy upstream hosts)
Back to load testing
Routing and DNS
Learnings
Extending Envoy: Niantic Frontend
Why Niantic chose Envoy