Writing better multi-process hybrid apps with React and Redux
summary
Builds Activity Stream for Firefox using React and Redux and shows concrete patterns that cut IPC complexity: replace per-action promises and many listeners with actions-as-messages plus middleware so the system uses single listener per channel, reducing memory‑leak vectors and making actions easy to test. Moves the Redux store into the parent process, hydrates tabs with a hydratable reducer, and handles complex side effects with redux-saga (also highlights redux-loop). The approach ships and fixes the original “bad time” issues.
AI-written summary · about
chapters (22)
- 0:00Start
- 0:42The S.P.A.
- 1:30Multi-process and multi-platform
- 7:41Lots of concurrency
- 8:25React View, Redux Store
- 8:49Dispatching "thunks"
- 9:31Thunky message passing
- 10:13On the parent process
- 12:31flux-standard-action
- 13:31Action-based model: middleware
- 14:16In the parent process
- 14:51Content process: store enhancer
- 16:09Higher order actions
- 16:36Limitations
- 19:04Create a parent store
- 19:35Initialization
- 19:47Hydrate child redux store
- 21:06Propagating changes - middleware
- 23:56Create a saga
- 24:41"Putting" actions
- 24:58Forking saga
- 26:10redux-loop
related talks
51mBuilding React Applications with Redux
49mRedux, beyond React
43mCleaning the Tar: Using React within the Firefox Developer Tools
45mRedux and Redux-saga to manage states in a large React app
23mHow we’re embracing functional programming to build a large SPA
51mRedux, beyond React
25mUniversal React Applications with Redux
36mThe Flux Pattern: MVC Framework for Data