Why GraphQL Between Microservices Is the Worst & Best Idea
summary
Claim: GraphQL between microservices is both harmful and powerful depending on where execution runs. Demonstration uses GraphQL Mesh to generate GraphQL schemas from OpenAPI → GraphQL, gRPC, SOAP, SQL and merge them without changing services. Demo links a public places API to a weather API with zero GraphQL code, exposes a single merged schema, and runs orchestration at the consumer side because execution runs anywhere. Result: working prototype and published library that already supports multiple handlers and modular sharing.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:38Intro to GraphQL
- 4:57The back-end
- 9:43GraphQL Mesh
- 12:28Demo
- 15:17GraphQL Mesh continued
- 16:24Public Mesh modules
- 19:03Summary
related talks
51mWhy GraphQL is Perfect for Microservices
27mWhy GraphQL is Perfect For Microservices
14mGraphQL Mesh – Query Anything, Run Anywhere
49mGraphQL Meshes
37mGraphQL and Microservices or How we learned to be big and small at the same time
01h 13mFrom Monolith to Microservices and Back
20mService-to-service GraphQL: The New Sweet Spot!
30mWhy GraphQL vs. Why not GraphQL