The Sched app allows you to build your schedule but you must also be registered for GraphQLConf 2026 to participate in the sessions.
Please note: This schedule is automatically displayed in Pacific Daylight Time (UTC-7). To see the schedule in your preferred timezone, please select from the drop-down located at the bottom of the menu to the right.
IMPORTANT NOTE: Timing of sessions and room locations are subject to change.
Sign up or log in to add sessions to your schedule and sync them to your phone or calendar.
React Server Components (RSC) and GraphQL have considerable overlap in the problems they seek to solve. This makes them competitors in some scenarios.
In this talk we’ll recount the origins of RSCs at Meta as a prototype within the Relay GraphQL client, discuss how to choose between the two technologies, and end with an exploration of architectures in which they both might reasonably coexist moving forward.
Jordan has spent the last nine years working at Meta. He currently works on Relay, a sophisticated GraphQL client for JavaScript that powers most of Meta's JavaScript applications.
Using GraphQL for service-to-service communication has historically been....frowned upon. Certainly, in isolation, there are compelling alternatives (gRPC, thrift, good ol' REST).
But in the age of LLMs and SDUI (Server Driven UI), there's lot of data whizzing around microservices. Does GraphQL fit this use case? I'll argue...yes!
You could define your data models with a combination of REST, gRPC, GraphQL; each layer gets a different transport protocol. Or we could consolidate on GraphQL.
This talk lays out why and when this makes sense, and what patterns are helpful to achieve this.
(ATTN: CFP reviewers -- fwiw the title is referencing https://productionreadygraphql.com/blog/2020-05-14-sweetspot)
