Ember and GraphQL in Practice
summary
Klockner replaces awkward JSON:API patterns with GraphQL to simplify a shopping-cart app: single-query deep fetching replaces multiple requests, and a bulk update mutation changes many line items without loading them into the store. Client choice is Apollo via ember-apollo-client, tests use a custom handler addon ember-cli-mirage-graphql or recorded responses with PollyJS. Result: fewer network calls, simpler model code, easier schema-driven exploration, and noticeably faster developer flow.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 2:26Why consider GraphQL
- 9:53GraphQL basics overview
- 14:36Choosing an Ember GraphQL client
- 16:43Implementing GraphQL in Ember
- 23:40GraphQL mutations and data flow
- 24:04Testing GraphQL with Ember
- 30:09Summary and takeaways
related talks
29mWrite Queries, Not Code
24mGraphQL and me
24mThe future of Angular client-server communication with GraphQL
41mThe GraphQL Way: A new path for JSON APIs
43mGraphQL in the Era of Server Components
55mGraphQL - APIs the New Way
01h 00mGraphQL - A query language to empower your API consumers
36mGraphQL Will Do To REST What JSON Did To XML