GraphQL for people who don’t need it
summary
About half the room already uses GraphQL and the concrete claim is that for many apps GraphQL is just a request/response schema sitting between JSON and your types, not a new service to run. Example: simple setGreeting/getGreeting RPC becomes a typed schema that compiles and rejects mismatches; GraphiQL gives autocomplete and exploration; you can wrap request in "query" field and still use URLSession or Postman; it keeps same auth and middleware and offers a GraphiQL autocomplete console with type checks and TDD-friendly tooling.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:30API
- 1:39Postman
- 1:55UI
- 2:20Function signature
- 3:00Explore your API
- 3:45Whats the catch
- 4:10Making a request
- 4:49GraphQL Response
- 4:59SetGreet
- 5:41HTTP Endpoints
- 6:35Why GraphQL
- 7:56GraphQL specifications
- 8:18Why use GraphQL
- 8:45GraphQL is not a microservice
- 9:11Decision tree
- 9:56Scale
- 10:14Post
- 11:57GraphQL Chaos
- 12:26Who does GraphQL
- 12:37Summary
