Why GraphQL is the "glue" for composable commerce

on YouTube ↗24m

" summary

Argues that GraphQL sits on top of REST and becomes the integration layer for composable commerce by fixing over-fetching and under-fetching and eliminating chains of 5–15 synchronous REST calls from clients to microservices (pricing, catalog, promotions). Claims server-side GraphQL aggregates many REST APIs in low-latency cloud calls, reducing per-client aggregator sprawl (commonly 2–4 aggregators) and enabling schema stitching with tools like Apollo. Notes GraphQL originates 2012–2015, spec released 2015 and donated 2017, and is a 216-page specification.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 6:12Under-fetching
3. 7:54Lack of Standardization
4. 10:07Option 1: Call Each API Separately
5. 10:51Option 2: Use Aggregator (Back End for Front-end)
6. 19:39GraphQL Specification

" related talks

• 33mGraphQL Will Do To REST What JSON Did To XMLRoy Derks · NDC London 2019
• 37mGraphQL — A New Look at the APIVladimir Zaets · JavaScript fwdays'18
• 23mHarnessing the Power of GraphQLJaeriah Tay · Front-End Foxes Day 2022
• 19mHow GraphQL accelerates B2B Composable CommerceMarco Egli · GraphQL Scale 2022
• 30mWhy GraphQL vs. Why not GraphQLSupriya Aggarwai · NodeJs Day 2019
• 51mWhy GraphQL is Perfect for MicroservicesRoy Derks · JNation 2022
• 24mGraphQL and meFaduma Mohammed · NodeJS Italian Conference 2018
• 22mWhy Migrate from REST to GraphQL?Erik Andersen · Commit Your Code 2024