GraphQL in the Era of React Server Components
summary
Compares React Server Components (Next.js/Remix) doing direct data fetches or even SQL from components with GraphQL’s role as a federated BFF for multi-team apps, argues RSCs work great for indie projects while GraphQL still wins for reusability across services, recommends GraphQL Federation plus the Relay compiler for fragment-driven queries and efficient component data, highlights TypeScript generation and an Explorer feature called talk to your schema that uses LLMs to generate executable queries.
AI-written summary · about
chapters (11)
- 0:00Introduction to GraphQL and RSC
- 2:34What are React Server Components
- 4:43Do you still need GraphQL with RSC
- 6:29GraphQL's original purpose
- 10:03When to use GraphQL today
- 12:53GraphQL as a BFF
- 15:23RSC as a lightweight API
- 17:09GraphQL clients and Relay
- 21:48Combining RSC with GraphQL
- 23:55GraphQL and AI integration
- 26:42Summary and Q&A
related talks
21mReact Server Components Vs. GraphQL
43mGraphQL in the Era of Server Components
18mIs a GraphQL BFF Necessary in a Server Side React World (RSC, SAs)?
47mReact, Relay and GraphQL — a perfectly normal component approach
09mGraphQL and React - Two Great Tastes that Taste Great Together
57mGraphQL in a Component World
05mYou Don't Need a Fancy Framework to Use GraphQL with React
27mReact State Management In a GraphQL Era
