GraphQL: advantages, challenges, and how to overcome them
summary
Explains concrete trade-offs and a live demo using IBM API Connect and an Apollo backend to show how GraphQL cuts calls (example slide drops 24 calls to 2) while creating expensive queries (examples ask 1,000 or even 1,000,000 records). Shows specific mitigations: schema editing to remove sensitive fields, augmenting types with cost-weighted limits and slice sizes, exposing a /cost endpoint, product plans that quota by query cost not call count, analytics (Elastic stack) surfacing 409 throttles, and mentions the open source openapi-to-graphql tool.
AI-written summary · about
chapters (15)
- 0:00Start
- 6:02Native Support for Graphql in Ibm Api
- 7:19Overview of What Graphql Is
- 8:13Recap of What Graphql Is
- 8:33Linux Foundation Has Announced the Graphql Foundation Initiative
- 11:19Why Is Graphql Getting Popular
- 13:37A Graphql Interface
- 16:11Should I Use Graphql
- 20:16Graphql Endpoint
- 20:43Graphic Query Language Editor
- 25:26Protect this Graphql Api with Api Connect
- 29:52Graphical Schema Editor
- 34:02Graphql Voyager
- 45:24How To Deal with Subscriptions in the Api Manager
- 47:13Authorization
related talks
30mWhy GraphQL vs. Why not GraphQL
40mGraphQL: A Case Study
30mFrom RPC to GraphQL"APIs from Past to Present"
23mHarnessing the Power of GraphQL
19mGraphQL: Accelerating Digital Transformation Through Modern APIs.
19mBringing GraphQL to the Enterprise: When IBM met Apollo
31mGraphQL: how to make clients enjoy using your API
54mGraphQL — Usable API or Just Another Hype?