Transcending microservice constraints in search of supergraph nirvana
summary
Argument: supergraphs give monolith cohesion on a federated microservice fabric by composing queries across sources so frontends make one call and get unified results. Implementation uses Hasura with a connector-first approach, a data loader pattern to eliminate n+1 joins, and predicate pushdown so authorization rules compile into SQL. Demo connects Postgres, Mongo and a loyalty store via JWTs, successfully returning user profile KYC and points in a single optimized query.
AI-written summary · about
chapters (13)
- 0:00Supergraph architecture intro
- 1:12Software architecture evolution
- 3:18Microservices to data products
- 5:47Microservice complexity challenges
- 7:31What is a supergraph
- 8:55Supergraph history and definition
- 9:56Supergraph design principles
- 11:41Composability's critical role
- 12:23Hasura supergraph implementation
- 13:27Supergraph authorization and governance
- 15:15Metadata and policy integration
- 16:20Live supergraph setup demo
- 18:50Querying multiple data sources
related talks
51mWhy GraphQL is Perfect for Microservices
08mGraphQL: everything you want in one query
06mEscape the GraphQL Monolith
37mGraphQL and Microservices or How we learned to be big and small at the same time
27mWhy GraphQL is Perfect For Microservices
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
36mGraphQL Federation - The @key to Your Platform API Strategy
36mThe Humn Side of GraphQL