Migrate your APIs to GraphQL: how? and why!
summary
Expedia migrates tens of heterogeneous REST APIs into per-domain GraphQL services behind a schema-composing reverse proxy, exposing a single endpoint so front ends see one cohesive API; teams use Spring Boot + graphql-kotlin (on GraphQL Java) to generate schemas from POJOs, 500+ developers roll services independently and deploy multiple times a day, and automated schema-driven deployment checks plus GraphQL schema composition catch breaking changes and show who still uses fields.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:00Context
- 1:50One API
- 3:05Too many API
- 6:30Domain services
- 12:50BFFs
- 14:55REST API
- 17:55Build a new API
- 18:55Build a cohesive API
- 21:30The abstraction layer
- 23:23The graphical layer
- 25:50The graphical Java layer
- 28:45Creating a graphical schema
- 31:58Discoverability
- 33:39Interfaces
- 36:46Schema
- 44:06Reporting
