Spring Time: From REST to GraphQL
summary
Demonstrates migrating a REST-heavy DJ app to Spring GraphQL with an Angular micro‑frontends client using Apollo; it implements a single /graphql endpoint, SDL schema as the API contract, resolvers wired to Spring services, and subscriptions via WebSocket implemented with Project Reactor Flux for live crowd-vote updates. Error handling returns HTTP 200 with GraphQL errors, tests use GraphQL test slices plus ArchUnit, and the live demo (QR vote → mutation → pushed update → audio) works end-to-end. Decision guidance: prefer REST for simple single consumers and HTTP caching; pick GraphQL for many varied clients and additive schema evolution.
AI-written summary · about
chapters (12)
- 0:00Introduction to Spring GraphQL
- 3:58REST scaling limits
- 7:29GraphQL exact requests
- 13:05GraphQL schema definition
- 17:17Spring GraphQL wiring
- 22:58Field resolution and errors
- 27:10Testing GraphQL with ArchUnit
- 29:58GraphQL subscriptions
- 35:14Micro front-ends and BFF
- 41:14Crowd votes demo
- 45:28REST vs GraphQL criteria
- 49:00Summary
related talks
50mObserving Spring for GraphQL in Action
59mGoodbye REST; Hello GraphQL
52mWelcome, Spring for GraphQL
47mMoving beyond REST: GraphQL and Java & Spring
01h 02mBootiful Spring GraphQL
18mCrafting compelling real-time web experiences with GraphQL
41mDoes Your API Need a REST? Check Out GraphQL.
38mModernize your Angular apps with GraphQL