The Humn Side of GraphQL
summary
GraphQL becomes the central data layer for a Go microservice stack on AWS using AppSync, Kafka, Apache Flink, DynamoDB and OpenSearch; a naive string-based client caused duplicated queries, brittle schema mismatches and heavy test boilerplate, and a hot path forced writes straight to OpenSearch for latency reasons. A v2 client built around code generation produces concrete Go types for every query and mutation, eliminates most query-string bugs, shrinks unit tests and is now rolling out across services.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 6:02GraphQL Schema
- 8:16GraphQL Queries
- 12:15Configurable Variables
- 13:06GraphQL Summary
- 13:41GraphQL In Humns Architecture
- 15:47AWS AppSync
- 18:30Considerations
- 21:05Simple Go Client
- 23:27A GraphQL Package
- 25:33Testing at Humn
- 27:41GraphQL Issues - Testing
- 29:24GraphQL Issues - Unit Testing
- 30:50The Way Forward
- 34:06Code Generation
related talks
20mScaling GraphQL on AWS: Production Architecture for High-Volume Data Systems
20mHumble GraphQL
28mGraphQL at scale with AWS
37mGraphQL and Microservices or How we learned to be big and small at the same time
24mGoing GraphQL
38mAPI Modernization with GraphQL
27mTransforming GraphQL: Infrastructure as Code for Front End Developers
20mService-to-service GraphQL: The New Sweet Spot!