GraphQL: A Case Study
summary
LeanIX reports on one year of production GraphQL use, describing concrete choices: embedding GraphiQL in the admin UI for developer testing, using a single generic patch mutation with transactions for create/update instead of many endpoints, and building a custom Apollo‑like client (not Apollo Client) to keep caching control. They handle the N+1 problem via pre-batch fetching and indexing, wrap exceptions to return user-friendly validation errors, and continue to use REST for simple CRUD operations alongside GraphQL.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:23Agenda
- 2:20IT Architectures are more important than ever before
- 5:06History
- 5:53Basic idea
- 6:59Why GraphQL?
- 10:48GraphiQL - Interactive in-browser GraphQL IDE
- 12:32Connections – Inspired by Relay Framework
- 14:20Connections – Advantages
- 15:26Connections – Lessons learned
- 16:32API Design – No "dead ends"
- 17:18API Design – General lessons learned
- 19:10GraphQL client – Query building
- 20:14What about the Apollo Client?
- 21:05So, what about it then?
- 22:03Mutations
- 25:32What is the N + 1 Select Issue?
- 28:51How To Solve This
- 30:27Exception Handling
- 31:49Conclusion
- 34:36Breaking News
related talks
31mGraphQL: how to make clients enjoy using your API
37mGraphQL — A New Look at the API
58mGraphQL -- Flexible APIs for Adaptive Clients
51mGraphQL: advantages, challenges, and how to overcome them
33mGraphQL - the What, how and why
35mGraphQL in real life
55mGraphQL - APIs the New Way
19mGraphQL: Accelerating Digital Transformation Through Modern APIs.