Unify Data Sources with GraphQL at the Edge
summary
A unified GraphQL layer combines MongoDB, Neon/Postgres, OpenAPI (Stripe), Contentful and remote GraphQL into a single schema, runs custom TypeScript resolvers at the edge, and ships an engine in Rust compiled to Wasm deployed on Cloudflare. The product includes an SDK for local-first development, per-field edge caching, auth rules (OIDC/JWT/RBAC), and a new IDE Pathfinder (beta); the core engine is now open source so teams can deploy the same stack anywhere.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 3:09Problem with scattered data sources
- 5:56Unified GraphQL API at the edge
- 8:44Demo setup and SDK overview
- 11:54Custom resolvers and extensions
- 13:40Authentication and caching
- 14:42Live demo with Pathfinder
- 15:46Closing and Q&A
related talks
55mGraphQL from the Ground Up
32mModernize development and activate legacy data with GraphQL
28mFederating the Content Layer
23mUnifying data with
55mGraphQL - APIs the New Way
19mSupport unlimited customer experiences with GraphQL
24mI’ve finally seen the light, the future is a graph
29mHow to Build a Unified GraphQL API