Adopt GraphQL without Writing any Backend Code
summary
Three concrete tactics to adopt GraphQL without touching backend code: GraphQL on the client runs graphql-js in the browser so components declare queries and the client auto-orchestrates resolver logic, cutting the two thirds of UI time spent wiring data; Apollo Link REST lets GraphQL queries map to existing REST endpoints and mix local store, REST and GraphQL calls in one client; GraphQL Mesh auto-converts OpenAPI/Swagger/gRPC/other schemas into a unified GraphQL schema so multiple APIs are stitched and queried as one.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:29What is GraphQL
- 4:43How GraphQL works
- 6:44Where to adopt GraphQL
- 8:48GraphQL on all components
- 9:44Benefits of GraphQL
- 10:56Implementing GraphQL
- 18:10GraphQL Mesh
- 20:26Summary
related talks
23mGradually Adopt GraphQL Without Writing any Backend Code
29mWrite Queries, Not Code
28mGraphQL without GraphQL - Backend Agnostic GraphQL inspired Queries For Colocating Data Requests With Components
31mGraphQL Without GraphQL: Backend Agnostic Requests with GraphQL Style Querying
32mFrom learning to thinking in GraphQL
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
31mReimagining the frontend-backend divide thanks to GraphQL
31mGraphQL: how to make clients enjoy using your API