Flux over the Wire
summary
A concrete implementation of flux moves stores to the server and carries actions and updates over WebSockets using socket.io; Nexus flux and Nexus flux socket.io implement symmetrical flux, react Nexus provides component-level subscriptions and an example app react Nexus chat; subscription batching cuts redundant streams (example reduces six subscriptions to three), server-side rendering fetches data first and returns HTML plus fetch data for immediate load, and the system runs in production at tens of thousands of concurrent users.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:24What React does
- 1:14Not all app state is local . User preferences
- 2:27Shared state with Flux
- 6:42Symmetrical Flux
- 7:57Flux over the Channel
- 9:06Flux over the Wire
- 10:29Chat with Fotw
- 12:03Introducing Nexus Flux
- 13:04React Nexus decorators
- 14:36React Nexus subscriptions batching
- 18:06React Nexus server-side rendering
- 19:31React Nexus in the real world
- 20:23Ideas to take home
related talks
31mFlux Panel
46mHow I learned to stop worrying and loved the flux
45mReactive web services
31mFlux: Utilize unidirectional data flow ...
30mCombining React and Websocket (...)
17mSyncing stores using socket streams
25mFlux Architecture with Xamarin
31mApplying Unidirectional Data Flow Beyond the ReactJS Ecosystem