Why Migrate from REST to GraphQL?

on YouTube ↗22m

" summary

Yum Brands migrates a large REST microservice landscape into one e-commerce platform in six months, then discovers maintenance pain from duplicated APIs and inconsistent IDs. The claim: switching to GraphQL reduces overfetching, enforces types-as-docs, and lets a GraphQL router stitch subgraphs so one client call aggregates checkout cart product and inventory data. Demo uses Node TypeScript, local subgraphs and Apollo-style tooling to enforce schema checks and catch breaking changes before deploy.

AI-written summary · about

" chapters (10)

1. 0:00Migration journey intro
2. 2:19Yum Brands challenges
3. 4:05REST pain points
4. 6:13GraphQL solves inefficiencies
5. 8:01GraphQL governance benefits
6. 10:50GraphQL fundamentals
7. 11:14Demo setup
8. 16:39Router and subgraphs
9. 17:22Querying demo
10. 21:44Summary and recommendations

" related talks

• 42mFrom REST to distributed GQLIgor Kasyanov · Python fwdays'19 online
• 29mFrom REST to GraphQLMarc-André Giroux · Full Stack Fest 2016
• 33mGraphQL Will Do To REST What JSON Did To XMLRoy Derks · NDC London 2019
• 36mGraphQL Will Do To REST What JSON Did To XMLRoy Derks · FrontCon 2019
• 49mMigrate your APIs to GraphQL: how? and why!Guillaume Scheibel · Devoxx Belgium 2019
• 37mGraphQL — A New Look at the APIVladimir Zaets · JavaScript fwdays'18
• 24mGraphQL in Production: Empowering Efficient Data Retrieval and Unleashing Developer ProductivitySeddik Benaissa · GraphQLConf 2023
• 23mHarnessing the Power of GraphQLJaeriah Tay · Front-End Foxes Day 2022