Adoption of GraphQL in Meta Ads Manager
summary
Ads Manager migrates from REST/Flux to Relay+GraphQL incrementally, replacing thousands of brittle selectors across a codebase of millions of lines by co‑locating data and refactoring components surface‑by‑surface. Engineering builds live resolvers to expose existing Flux stores as GraphQL fragments, a flux‑on‑relay wrapper to let both stacks coexist, and runs broad shadow validation (compare outputs and latency) until 4–5 nines parity before shifting traffic. The migration yields progressive reliability and observability gains, tooling (linters, codegen) lowers per‑team friction, and measured performance overhead proves negligible on critical surfaces.
AI-written summary · about
chapters (9)
- 0:00Introduction to ads manager
- 2:45Engineering challenges
- 6:19Benefits of Relay and GraphQL
- 8:46Architectural migration strategy
- 12:09Evaluation of migration paths
- 16:01Implementing the iterative path
- 20:09Backend transition and validation
- 23:20Organizational and cultural shift
- 26:05Q&A session
related talks
29mIncrementally Adopting GraphQL and Relay at Pinterest
22mWhy Migrate from REST to GraphQL?
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
31mFrom Relay to Apollo, a story of GraphQL clients
25mDemystifying GraphQL Clients
35mUsing GraphQL and Relay for hybrid RoR apps
27mData fetching for React applications at Facebook
01h 00mPowering the Front-end with React, GraphQL and Relay