Stranger Graphs - Building Federated Workflows with Shared Components
summary
Claim: building a Federated design system of domain-specific components on top of GraphQL federation cuts UI duplication and speeds delivery. Uses GraphQL federation with 300+ subgraphs, TypeScript + React, fragment-driven packages generated by GraphQL Codegen, and an Elasticsearch-backed Netflix Graph Search. Teams publish three-layer packages (fragments, fetch/data layer, composed UI recipes), assign an IC owner, and ship reusable taskboards with commenting, history and search; search UIs go from index-ready to production in a day or two, reducing duplication and clarifying ownership.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 3:35Content Finance workflows at Netflix
- 8:31Challenges with federated data and UI
- 10:17Federated design system solution
- 13:50Building the federated design system
- 17:38Examples of federated components
- 24:52Future work and Q&A
related talks
38mGraphQL Federation in the Wild
20mThe State of GraphQL Federation
16mSponsored Session: Federation, Reversed: A Consumer-First Future with Fission
23mBlueprints of Successful GraphQL Architectures
24mRethinking frontend architectures with data layers
31mReimagining the frontend-backend divide thanks to GraphQL
30mDeep Learnings Migrating legacy services to Federated GraphQL
50mDistributed Architectures for Distributed Teams