Flux Panel

on YouTube ↗31m

" summary

Panel explains concrete tradeoffs: Relay and GraphQL aim at large apps while Flux stays general; Power Editor keeps data fetching in stores across 106 stores and cuts controller updates from 237 to 58 on load (and from 87 to 24 on change) by debouncing post-dispatch; alternatives keep fetches in action creators for optimistic updates; isomorphic Flux appears as store instances with dehydrate/rehydrate versus server singletons (Nashorn on Scala demonstrated); routing via a route store and container/UI component split are shown.

AI-written summary · about

" chapters (13)

1. 0:00Introduction
2. 2:05Flex and Relay
3. 8:20Interface Optimization
4. 10:30Dependencies
5. 12:25Components
6. 14:45Store instances
7. 16:00Stores per request
8. 17:00Store Collisions
9. 19:40Nashhorn
10. 22:15Airbnb
11. 24:35App Model
12. 26:10Relays
13. 28:15Route Stores

" related talks

• 25mA cartoon guide to the wilds of data handling in ReactLin Clark · JSConf US Last Call 2015
• 26mFlux over the WireElie Rotenberg · ReactEurope 2015
• 25mA Cartoon Guide to the Wilds of Data HandlingLin Clark · React.js Conf 2016
• 59mReact, Flux and the Right AbstractionsYlia Seheda · OdessaJS 2015
• 46mHow I learned to stop worrying and loved the fluxJaseem Abid · Meta Refresh 2015
• 45mAn Overview of the React EcosystemRami Sayar · Spotlight React 2016
• 36mThe Flux Pattern: MVC Framework for DataRob Richardson · Developer Summit 2020
• 42mQ&A Panel with Core team and speakersReactEurope 2017