Having Your Cake and Eating It Too GraphQL in Reason
summary
Claims that compile-time GraphQL+Reason guarantees client-server safety and shows working tooling: editor autocomplete, generated React components from queries, and CI that fails builds if a schema change would break clients. Demos include a Spotify end-to-end DJ app built with ReasonReact plus WebRTC that works, an 11‑API call mashup completing in ~1.2s, and native hot‑swap of binaries in tens of milliseconds. Server support uses ocaml-graphql-server and the talk notes remaining pain points.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:44Spotify REST API
- 11:16Graphical Explorer
- 13:07Shipping a Graphical API
- 14:09Generating Schema Change Log
- 14:45Mocking
- 16:43GraphQL REST
- 18:19GraphQL REST Example
- 23:47GraphQL introspection
- 27:46Javascript challenges
- 28:51Reason challenges
- 32:38Reason vs React
- 35:40GraphQL React
- 36:59Hot Reloading
- 38:03Summary
- 38:51Backend
related talks
37mHaving your cake and eating it too — GraphQL in Reason
30mGraphQL in the Era of React Server Components
24mBuilding Reactive GraphQL Apps With Apollo
58mCrafting compelling real-time web experiences with GraphQL and React
30mReact state management in a GraphQL era
43mGraphQL in the Era of Server Components
18mCrafting compelling real-time web experiences with GraphQL
21mReact Server Components Vs. GraphQL