Transpiling GraphQL instead of writing customized....
summary
Claim: GraphQL queries are transpiled at runtime into JavaScript-flavored functions that explicitly fetch and compose data across services and databases, so APIs require no handwritten resolvers. The system augments the schema with data-access metadata, walks the query AST plus type info, targets an internal query language, and emits per-query code that handles batching, errors, access control and returns exactly the requested shape. Teams add schema metadata to expose data and get updates without deploys because each query becomes a specialized function generated on demand.
AI-written summary · about
chapters (8)
- 0:00Introduction to transpiling GraphQL
- 1:27Example user timeline API
- 3:35GraphQL query breakdown
- 6:27Typical GraphQL resolvers
- 10:51Goals for improvement
- 13:39Transpiling queries to code
- 20:23Results and future work
- 22:49Q&A session
related talks
37mGraphQL — A New Look at the API
16mIntro to GraphQL
27mGraphQL: Towards a universal query language
32mFrom learning to thinking in GraphQL
28mExploring GraphQL
11mCompiling GraphQL to Blazing Fast JS
23mGradually Adopt GraphQL Without Writing any Backend Code
28mGraphQL without GraphQL - Backend Agnostic GraphQL inspired Queries For Colocating Data Requests With Components