Clients in control: building demand-driven systems with Om Next
summary
Claims a client-driven data model where Om Next uses a query language, a parser runs on client and server to interpret component queries and mutations, and normalized state that replaces duplicates with identity links. Demonstrations include optimistic mutations with temporary client IDs auto-mapped to persisted IDs, selective re-rendering of affected subtrees, property-based testing with test.check that finds and shrinks real UI bugs, and integration patterns with GraphQL/Falcor ideas and server-side rendering.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:23REST: expectations
- 1:42REST: reality
- 5:24Demand
- 6:05Composition
- 6:45Interpretation
- 14:25Om Next opinions Single source of truth
- 17:17Parser
- 19:50Creating information
- 20:35Client-only state
- 21:35Normalization
- 23:22React render
- 25:15Property-based testing
- 30:03Testing recap
- 32:28Server
- 33:36Project status
related talks
46mOm Next
37mAll you need is l̶o̶v̶e Apollo Client
21mHow Next.js is delivering React’s vision for the future
23mOptimistic UI updates with Apollo Client and React
44mHow to Approach Modern Web Applications
41mDemand Driven Applications with GraphQL by Vinci Rufus
27mThe Functional Final Frontier
01h 00mArchitecting Data-Driven Apps for UX Success