Modernize your Angular apps with GraphQL
summary
Claims that replacing REST with GraphQL cuts multiple client requests into one request, that a schema enforces typed queries so client and server agree, and that the Angular demo uses the Angular-Apollo client to merge component queries automatically. The uploader-provided Angular2 example actually runs against a Star Wars API, shows fewer network round trips versus REST, and works live on a slow network during the demo.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:53Brief general overview of GraphQL
- 6:08Why should Angular developers care about GraphQL
- 10:08The problems of REST
- 15:53Rethinking data fetching
- 18:30GraphQL example
- 23:32A Modern web app with GraphQL
- 25:05More features of GraphQL
- 28:08Live Angular2 GraphQL example
- 33:28Misconceptions about GraphQL
- 35:07Summary
related talks
24mThe future of Angular client-server communication with GraphQL
26mAngular and GraphQL – A modern API for a modern Platform
11mAngular 2 love at first sight with GraphQL
46mUnleashing the power of GraphQL using Angular 2
45mComponent based API for your Angular Components with GraphQL
26mAngular + GraphQL. We do it because we can!
59mGoodbye REST; Hello GraphQL
28mGraphQL-Anywhere
