An Unconventional Approach to Choosing a Client GraphQL Library
summary
A team at Revolut describes introducing GraphQL into a large project, how they organized server and client data storage and management, and why they chose MST-GQL over apollo-client. The talk compares pros and cons of different GraphQL client-library approaches and highlights practical problems to watch for.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:08Company and project
- 3:14Local data state issues
- 5:03Why not Apollo Client
- 6:50Apollo local logic issues
- 8:15Apollo dual approach issues
- 9:41GraphQL client alternatives
- 10:43MobX and GraphQL solution
- 12:07MobX GraphQL client workings
- 13:10Implementation example
- 14:11MobX GraphQL pros and cons
- 14:53Apollo vs MobX GraphQL
- 15:35Recommendations
related talks
32mSponsored Session: Championing GraphQL Client in a Modern Platform
31mGraphQL: how to make clients enjoy using your API
47mGraphQL: How to Persuade the Server to Fit the App
14mKeynote: GraphQL Clients in 2024
30mWhy GraphQL vs. Why not GraphQL
15mThe State of GraphQL Clients in 2023
03h 00mUnderstanding GraphQL
47mGraphQL for Grown-Ups: Introducing the Technology into an Old Project Without Youth Frameworks