Go from being skeptical about Relay to falling in love with it
summary
Explains why Relay replaces repeating GraphQL wiring with concrete mechanisms: a compiler that gives automatic fragment imports and data masking, client-side directives that enable fragment-level variables/arguments, and per-fragment refetch per-node via global ID so only one fragment reruns instead of the whole page. Shows Hasura adding Relay support, demos wiring to deployable endpoints, and reports the integration works in beta to eliminate redundant requests and surface compile-time errors.
AI-written summary · about
chapters (11)
- 0:00Intro
- 4:35One query per component
- 5:16A terrible idea
- 5:53One gigantic query
- 6:38Fragments
- 11:37Isolation and modularity
- 13:53Variables in fragments
- 16:54Updating fragments
- 17:37pagination
- 21:29Running a fragment by itself
- 23:20Summary
related talks
14mWhy Relay is a Must for your GraphQL APIs
12mRelay Concepts
09mCommon UI Problems & Scaling With Relay
32mReintroducing Relay
28mRelay: An Application Framework For React
01h 00mPowering the Front-end with React, GraphQL and Relay
31mFrom Relay to Apollo, a story of GraphQL clients
47mReact, Relay and GraphQL — a perfectly normal component approach