Humble GraphQL
summary
Uber runs several thousand microservices in a monorepo and introduces GraphQL for web front ends since 2019, resulting in 90% of web apps use GraphQL but with schemas generated one-to-one from protobufs so schema quality is intentionally sacrificed for adoption. CI enforces cross-validation and communal ownership; teams can pick an RPC track that uses generated protobuf types and the platform recommend react-query for client caching, or a GraphQL track built with Apollo and GraphQL Code Generator; ongoing work raises schema quality for core plugins (user, trip, order) and seeks to reduce fragmentation.
AI-written summary · about
chapters (9)
- 0:00Humble GraphQL intro
- 2:36GraphQL adoption issues
- 6:57Two years of GraphQL at Uber
- 9:06GraphQL benefits despite flaws
- 11:57GraphQL and RPC at Uber
- 13:45RPC and GraphQL in frontend
- 16:14Improving GraphQL schema
- 17:18Evolving GraphQL openly
- 18:21Q&A
