Why GraphQL Isn’t That Simple
summary
A Yandex engineer describes migrating backend services from REST to GraphQL for Yandex.RealEstate and Yandex.Rent, explaining how the team managed the GraphQL schema, why they implemented a custom GraphQL client, and how development processes changed after the switch. The talk also covers integration challenges encountered in a thick (monolithic) client and presents a fundamental BFF-level problem with a proposed solution.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:09Speaker background
- 3:36Yandex.Renta’s GraphQL choice
- 7:30First steps and adoption
- 8:15Schema First vs Code First
- 10:42Shifting development views
- 12:21GraphQL in different apps
- 13:30SSR problems with GraphQL
- 16:53Backend GraphQL tips
- 17:57Tooling challenges
- 20:11Building a GraphQL client
- 21:14Query structure and typegen
- 22:21Type generation role
- 24:59Error handling conventions
- 27:293-year GraphQL results
- 31:24Changes after adoption
- 32:54Q&A
related talks
22mWhy Migrate from REST to GraphQL?
46mFrom REST to GraphQL: A 20-Minute Adventure
30mWhy GraphQL vs. Why not GraphQL
37mAll in client GraphQL
46mMoving to GraphQL
47mGraphQL: How to Persuade the Server to Fit the App
31mGraphQL: how to make clients enjoy using your API
01h 07mGraphQL: Smooth Schemas and Rough Edges
