The Internal Lens: GraphQL Gateways From a Different Axis
summary
A separate internal GraphQL gateway unifies 15 upstream sources into one admin client, built on GraphQL Mesh v0, accumulating 2,000 types, 120 queries, 100 mutations and seven nesting levels after six years of operation. The gateway enforces an audit pattern where clients append a required “log audit event” with before/after state and reason, stores human-written markdown docs for business context, and admits repeated schema drift because a schema registry was not integrated into upstream CI. AI-assisted tooling is being piloted atop this lens.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 1:03Public vs internal GraphQL
- 3:07Building the internal gateway
- 4:51Gateway architecture overview
- 6:37Mindset for internal tooling
- 8:43Audit logging necessity
- 11:11Six years of revelations
- 11:31Gateway as organizational lens
- 13:40Unification challenges
- 17:53Documentation as human work
- 19:57Schema registry failures
- 21:02Future with AI integration
- 24:16Q&A session
related talks
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
33m6 Years of Distributed GraphQL in Production
49mGraphQL Meshes
01h 05mWorkshop: Scaling and Securing API Development with a GraphQL Platform
16mUnify Data Sources with GraphQL at the Edge
31mGraphQL: how to make clients enjoy using your API
40mGraphQL: A Case Study
15mHarnessing GraphQL for Efficient API Queries: Learn How