GraphQL and me
summary
Describes why GraphQL replaces brittle CMS responses for Vogue and GQ by moving business logic into a GraphQL layer, using Apollo and a client to collapse many REST calls into one query, cutting over‑fetching and coupling, producing instant schema documentation and type safety, and resolving data from multiple sources so the React app with server rendering and Redux only requests what it needs.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:30A lot of our components were tied very specifically to the API response.
- 9:21It is a business risk to couple your application to a third party service.
- 9:32The API was difficult to work with: it had some quirks that we didn't understand.
- 10:41We were fetching data in complicated ways from deep trees in the API every time.
- 13:40Instant documentation
- 15:03We no longer have to fetch data with multiple requests in our main application.
- 15:50It encouraged good patterns of structuring our app.
- 16:50Domain Driven Design Hexagonal Architecture
- 17:06We have the insurance that if we ever need to change our data source, most of our app will not be affected.
- 20:10You're building an application that uses multiple data sources.
- 22:04You want to enforce structure in your code base.
- 22:32You've built your REST API like a pseudo-GraphQL API anyway.
related talks
25mBuild the API you want to see in the world
37mGraphQL — A New Look at the API
36mGraphQL Will Do To REST What JSON Did To XML
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
29mWrite Queries, Not Code
33mGraphQL Will Do To REST What JSON Did To XML
23mBuild the API You Want to See in the World
17mThe Power of GraphQL