The Power of Strongly Coupled GraphQL Queries for Internal APIs
summary
Argues that single‑use, strongly coupled GraphQL queries for internal APIs cut payloads and speed up responses by pushing filtering and aggregation into the server, using Prisma to apply start/end date filters and SQL joins so clients receive rows-and-columns shaped results ready for React Table. Benefits: fewer client-side mappings, clearer separation of UI vs business logic, and smaller network cost. Tradeoffs: more backend mapping, duplicated page-specific types and longer type names like attendanceDashboardWeekday.
AI-written summary · about
chapters (8)
- 0:00Introduction to talk
- 1:09What is strongly coupled GraphQL
- 3:59Old approach problems
- 8:57New approach benefits
- 12:26Demo of new query
- 15:58Drawbacks of new approach
- 18:10Summary and conclusion
- 19:35Q&A session
related talks
23mHarnessing the Power of GraphQL
22m5 Antipatterns that Made Our React/GraphQL App Slow (And How We Fixed Them)
29mWrite Queries, Not Code
51mGraphQL: advantages, challenges, and how to overcome them
30mWhy GraphQL vs. Why not GraphQL
30mFrom RPC to GraphQL"APIs from Past to Present"
19mGraphQL: Accelerating Digital Transformation Through Modern APIs.
22m8 Years of GraphQL: Unraveling the Trade-Offs