~/talk

React Server Components Vs. GraphQL

Talkat GraphQLConf 2026 · on Tuesday, 2026-05-19· at 10:30· Boardroom· [react, graphql]
slides:none on file

Claims that React Server Components originated as a Relay prototype at Meta and that RSCs and GraphQL both expose the same model layer and avoid network waterfalls, but diverge on language and runtime tradeoffs. Relay 21 ships experimental APIs to fetch server-only data and hand it to the client; a TypeScript-side project called Grots maps a TS server to GraphQL. RSC wins for web when the server runs in Node and when needing optimal client bundles, GraphQL remains stronger for native apps and highly dynamic client-side updates. RSC+GraphQL coexists via a BFF pattern.

AI-written summary · about

  1. 0:00Introduction and background
  2. 1:04What are React Server Components
  3. 2:11Evolution of UI and data layers
  4. 5:48GraphQL’s role in bridging gaps
  5. 7:53SPA vs server-rendered trade-offs
  6. 9:59React Server Components as a solution
  7. 12:10Node vs non-Node server scenarios
  8. 13:54Caching and permissions importance
  9. 15:00React Server Components with GraphQL
  10. 17:11Current limitations of RSCs
  11. 19:16When to choose RSCs or GraphQL
  12. 20:16Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.