Building Relay Spec Compliance in Federation
summary
Describes how to make Relay’s connection and global object-identification rules work inside Apollo Federation by adding a dedicated node resolver that decodes opaque IDs, returns entity references and lets the gateway call subgraphs via entities. Shows IDs encoded as base64 TypeName:JSON(keyFields) so global uniqueness holds across services, explains cursor ordering for connections, and gives numbers (Wayfair runs >9 million product listings). Announces open source libraries node-freud (JS) and a Java port, supports Apollo contracts, handles nested keys and optional encryption callbacks.
AI-written summary · about
chapters (9)
- 0:00Relay spec compliance in Federation
- 2:10Relay’s connection specification
- 4:36Object identification in monoliths
- 10:12Object ID challenges in Federation
- 12:38Implementing object ID in Federated graphs
- 14:23Live demo: Federated node queries
- 18:39Introducing nodeFreud for Federation
- 20:24Relay spec adoption benefits
- 21:26Q&A
related talks
31mFrom Relay to Apollo, a story of GraphQL clients
12mRelay Concepts
14mWhy Relay is a Must for your GraphQL APIs
28mBuilding a distributed graph w/ Apollo Federation
48mApollo Federation: Connecting GraphQL Microservices
58mApolloClient or Relay with Fragments, ‘Hairy’ GraphQL and TypeScript
26mGo from being skeptical about Relay to falling in love with it
36mGraphQL Federation - The @key to Your Platform API Strategy