Moving beyond REST: GraphQL and Java & Spring
summary
Argues GraphQL can augment or replace REST by exposing a single schema-backed endpoint that avoids over-fetching and under-fetching. Demonstrates a Spring Boot server (H2 + Spring Data repositories) built two ways: low-level graphql-java and annotation-driven GraphQL SPQR. Shows GraphiQL explorer, runs queries against a Star Wars dataset (count returns 37 starships), performs mutations (adds a car that calls an external Giphy service), and notes pagination and auth still require explicit server work.
AI-written summary · about
chapters (45)
- 0:00Introduction
- 0:35What is Spring
- 1:40What is GraphQL
- 2:21Learning GraphQL
- 2:48API Query Language
- 3:13GraphQL
- 3:45Silicon Valley
- 4:27GraphQL vs REST
- 5:47GraphQL Data Sources
- 6:10GraphQL Endpoints
- 7:22Demo
- 8:26GraphQL Schema
- 11:50GraphQL Endpoint
- 15:16Query Parameters
- 16:08Recap
- 16:52GraphQL Query
- 18:11Antipattern
- 18:42What GraphQL enforces
- 20:31Avoid callback hell
- 20:58Update two unconnected objects
- 21:28GraphQL is faster than REST
- 22:57Removing fields
- 24:29Adding fields
- 25:03Explicit fields
- 25:15Magic in REST
- 25:33More concrete
- 26:05GraphQL fragment example
- 26:56GraphQL libraries
- 27:17GraphQL SPQR
- 27:35Data can be anything
- 28:00Wrap anything you want
- 32:21Why use Spring
- 32:56GraphQL Speaker
- 35:17Testing
- 35:49GraphQL Query Name
- 36:06Autogenerated GraphQL schema
- 36:35GraphQL docs
- 36:54Additional stuff
- 41:00Double Check
- 41:13Cool
- 41:34Flexibility
- 42:38GraphQL Controller
- 45:12Spring Command Line
- 45:45Slides
- 47:10Mutations
