Gradually Adopt GraphQL Without Writing any Backend Code
summary
Three concrete paths to adopt GraphQL without touching backend code: run a small GraphQL engine in the client with graphql-js/graphql-tools so resolvers execute and fields resolve in parallel; use Apollo Rest Link to annotate queries so one GraphQL query pulls from REST, GraphQL, and local store together; generate and stitch schemas with GraphQL Mesh from OpenAPI/Swagger/gRPC/SQL, merge city and weather APIs into one schema, produce autocomplete and predictable results, and run the generated SDK distributed or as a gateway in production.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:12Short intro to GraphQL
- 4:07Main benefits
- 6:21Questions
- 6:52GraphQL for product
- 11:16Making change
- 12:12GraphQL for product
- 16:40GraphQL Mesh
- 19:25Demo
- 21:58GraphQL Mesh
- 22:42Summary
related talks
22mAdopt GraphQL without Writing any Backend Code
28mGraphQL without GraphQL - Backend Agnostic GraphQL inspired Queries For Colocating Data Requests With Components
32mFrom learning to thinking in GraphQL
16mIntro to GraphQL
58mGraphQL -- Flexible APIs for Adaptive Clients
31mGraphQL: how to make clients enjoy using your API
24mA GraphQL Survival Kit
29mWrite Queries, Not Code