GraphQL-Anywhere - How GraphQL can improve your work across all of your stack
summary
Claims that running client-side GraphQL turns component data needs into declarative queries, replacing lots of reducer and service code; demonstrates a working WhatsApp clone and links code (WhatsApp-ngAtlanta) and a library called Luna smart store. Compares Luna to ngrx/Redux, Relay and Apollo, shows local fields merged with remote, cache flags to avoid redundant requests, and quotes ~2/3 time saved on data shaping. Practical tooling and examples are shown, not just high‑level diagrams.
AI-written summary · about
chapters (14)
- 0:00Intro
- 3:15Why GraphQL
- 5:32The problem
- 7:25PayPal example
- 8:49Database vs GraphQL
- 11:23What is GraphQL
- 13:13GraphQL Components
- 15:45Why Facebook doesnt use Redux
- 19:40Why you should switch from Redux
- 19:59What is Luna
- 20:57Integration with other frameworks
- 21:31NGRX
- 22:43Example app
- 26:53Summary
related talks
28mGraphQL-Anywhere
29mWrite Queries, Not Code
24mBuilding Reactive GraphQL Apps With Apollo
25mDemystifying GraphQL Clients
24mThe future of Angular client-server communication with GraphQL
30mReact state management in a GraphQL era
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
31mReimagining the frontend-backend divide thanks to GraphQL