Applying Unidirectional Data Flow Beyond the ReactJS Ecosystem
summary
Describes applying a Flux-style unidirectional data flow outside React by implementing small readable stores, a composer that aggregates multiple stores into complete models/collections, and a lightweight virtual DOM to avoid manual DOM diffs. Shows this approach implemented on Backbone/Marionette in production for two real-time lists (with websocket updates) without large rewrites, yielding cleaner views and precise incremental updates via simple read/save store interfaces.
AI-written summary · about
chapters (17)
- 0:00Unidirectional data flow challenges
- 2:21Need for new architecture
- 4:34Flux core concepts
- 7:01Flux in Backbone.js
- 9:13Rules for unidirectional views
- 11:22Data flow cycle interactions
- 12:29Modular business logic benefits
- 14:59Live coding demo
- 16:17Flux store example
- 17:44Composite store for aggregation
- 19:30Flux stores with Backbone views
- 20:56Simpler templates with Ractive.js
- 21:38Clean Backbone views
- 22:46Real-time updates with Ractive.js
- 23:59Social media feed demo
- 25:03Composite store for feed collection
- 26:17Q&A
related talks
25mA cartoon guide to the wilds of data handling in React
58mFrontin' like a Back-er
36mThe Flux Pattern: MVC Framework for Data
46mHow I learned to stop worrying and loved the flux
30mFlux for Data Visualization: A Preliminary Manifesto
34mFunctional UIs and Unidirectional Dataflow
27mReact, But For Data
30mReact: Rethinking best practices