Goodbye REST APIs. Hello GraphQL!
summary
GraphQL lets the client declare exactly the JSON it wants, including nested relationships and specific fields returned from mutations, so one POST to a single endpoint replaces many chattier REST calls. Demos use Node with json-graphql-server and express-graphql, GraphiQL for GraphiQL docs auto-generated autocomplete, JSON Server to mock REST backends, and a React + Axios client calling GitHub’s GraphQL API. Setup takes ~30–45 seconds and about 20 lines of server code to prove it works.
AI-written summary · about
chapters (24)
- 0:00Intro
- 2:07Getting Started
- 3:27GraphQL Docs
- 10:33Mutations
- 18:06How it works
- 19:35How it works again
- 20:44GraphQL Schema
- 23:55Wrap REST API
- 27:29GraphQL Demo
- 31:36React Demo
- 37:47GraphQL Development
- 42:05GraphQL Mutation vs Query
- 42:51Hashira GraphQL Engine
- 44:46What about caching
- 45:59What about failed fetches
- 47:16What about authorization
- 49:00Pain
- 51:52GraphQL
- 52:39Side Note
- 53:04GraphQL vs REST
- 55:28GraphQL popularity
- 56:39GraphQL is the new REST
- 57:21Rest vs GraphQL
- 58:28What is REST
