Building Modular Redux Applications
summary
Concrete rules: separate UI from data into independent modules, with presentation modules holding only components and UI state reducers/actions, and data sources holding fetching, storage reducers and data actions; connect them with a data provider higher‑order component that calls react-redux connect and selectors so data sources can be swapped without breaking components. Repository redux-seed implements the folder layout, example HOCs, and advice on avoiding inter‑module dependencies and excessive multi‑connect performance hits.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:31Building Modular Redux Applications
- 1:25The motivation for this talk
- 2:23So, what are we going to talk about?
- 2:54What is an application made of?
- 4:13Presentation Layer
- 4:48Data Layer
- 8:39Ducks
- 10:08Rules For Structuring (Redux) Applications
- 12:32What is a module?
- 14:27Separation of concern
- 16:40Data Provider
- 17:47Connecting Components
- 19:32Dependency Graph
- 20:16Application Structure
related talks
51mBuilding React Applications with Redux
19mThe elegance of decorated Redux
26mWhy I chose to modularize the ducks in my React App
48mWhy I chose to modularize the ducks in my React App
44mThe Fundamentals of Redux
25mScaling React.js Applications
27mHow to Write Bad Code in Redux
25mUniversal React Applications with Redux