Beyond REST: GraphQL API Management
summary
Explains that GraphQL shifts query complexity onto the API provider so one GraphQL request can trigger multiple backend calls, and that protects and monetizes APIs require more than simple rate limits. Describes using a gateway to analyze nesting depth and resolver complexity, precompute cost and reject heavy queries, and support differentiated API plans. Notes IBM’s open-sourced Node tool to convert REST to GraphQL and points to GitHub’s query scoring as a concrete example.
AI-written summary · about
chapters (16)
- 0:00GraphQL API Management
- 2:32GraphQL- The Value
- 5:59The 10 of APIs == Service Oriented Architecture (SOA)
- 7:17The 2.0 of APIs == REST
- 8:20Advantage: API Provider and API Consumer
- 8:37The 3.0 of APIs = GraphQL and Async Endpoints
- 9:59Advantage: API Consumer
- 10:21REST w's And GraphQL
- 12:49GraphQL Endpoints De-constructed
- 15:29Protection Via Throttling & Rate Limits
- 17:18API Management of Graphol
- 17:57GraphQL Management
- 23:46Query Analysis for Protection and SLA
- 24:45Threat Protection
- 27:14Differentiated API Plans
- 28:30Summary
related talks
51mGraphQL: advantages, challenges, and how to overcome them
23mHarnessing the Power of GraphQL
29mFrom REST to GraphQL
37mGraphQL — A New Look at the API
19mBringing GraphQL to the Enterprise: When IBM met Apollo
30mWhy GraphQL vs. Why not GraphQL
31mGraphQL: how to make clients enjoy using your API
18mIs GraphQL the end of RESTstyle APIs