Federating the content Layer
summary
GraphCMS exposes a single GraphQL endpoint that glues together REST and GraphQL backends (GitHub, npm, Shopify, AWS) via content federation using configurable remote fields and custom input types, with TTL caching and header mapping. The demo live-queries GitHub users and repos, merges those records with CMS documents, and returns one combined response; the feature is shipping in weeks and aims to reduce middleware and leverage edge caching to avoid a single point of failure.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:15Content Federation
- 6:08Content Delivery
- 7:26The Headless Cms
- 8:11Headless Cms
- 30:20Schema Editor
- 30:37Custom Types and Custom Input Types
- 32:06Create a Model
- 36:33Graph Cms
- 40:07Community Comments
- 43:30User Feedback
- 44:39Federation Graphql
related talks
28mFederating the Content Layer
25mFederating the Content Layer with GraphQL & Hygraph
23mShould E-Commerce Companies Move to a Headless GraphQL CMS?
37mThe Future of GraphQL in the Enterprise Panel Discussion by GraphCMS
19mSupport unlimited customer experiences with GraphQL
16mUnify Data Sources with GraphQL at the Edge
23mMCP: Is GraphQL the Right “Tool” For the Job?
24mGraphQL and me