Why REST APIs are dead and we should use GraphQL APIs
summary
Argument that RESTful HTTP APIs, while fine originally, struggle with modern complex products (especially mobile apps) and that GraphQL addresses those limitations. Covers the problems with traditional REST interactions and explains reasons to consider replacing RESTful APIs with GraphQL in many applications.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:50REST API problems
- 16:43GraphQL intro
- 19:31GraphQL basics
- 23:20GraphQL origin
- 29:23Queries and mutations
- 33:19Schema and typing
- 36:49Introspection and docs
- 40:00Implementation tools
- 43:07Learning resources
- 46:44GraphQL benefits
- 47:49REST vs GraphQL
- 48:30Q&A
related talks
39mWhy REST when you can GraphQL
18mIs GraphQL the end of RESTstyle APIs
49mGraphQL - When a REST API Is Not Enough
58mGraphQL Is Dead: Long Live REST APIs with Hypermedia
46mIntroduction to GraphQL - The Better REST?
27mA no nonsense GraphQL and REST comparison
12mUsing public APIs
22mAre REST APIs Still Relevant Today?