GraphQL in the Era of Server Components
summary
Claims GraphQL remains valuable when many frontends or microservices need one reusable API and federation; for one-to-one apps server components, REST or TRPC = TypeScript RPC are often simpler. Demonstrations use Nexus/Next.js server components, Relay/Apollo/urql clients and a JSONata adapter; a large language model reads the GraphQL schema and LM generates GraphQL operations to fetch customer and MySQL order data. Demo works end-to-end but sometimes fails and requires a human-in-the-loop to fix queries.
AI-written summary · about
chapters (9)
- 0:00Introduction to talk
- 3:05Server components vs GraphQL
- 6:57GraphQL’s original intent
- 10:32When to use GraphQL today
- 15:28GraphQL Federation explained
- 21:52GraphQL vs tRPC comparison
- 26:37GraphQL clients and Relay
- 33:32GraphQL and AI integration
- 40:58Summary and recap
related talks
30mGraphQL in the Era of React Server Components
24mThe future of Angular client-server communication with GraphQL
47mReact, Relay and GraphQL — a perfectly normal component approach
21mReact Server Components Vs. GraphQL
28mGraphQL Servers
59mGoodbye REST; Hello GraphQL
01h 00mGraphQL - A query language to empower your API consumers
29mWrite Queries, Not Code