Structure for Reduxs
Structure in Redux is how you organise state and code as an app grows. The recommended approach groups logic by feature, with one slice file per feature, normalised data for collections, and selectors that read and derive values. Good structure keeps components simple and avoids storing data that can be computed.
Stage: Patterns · Part of the Redux roadmap · Last reviewed 19 November 2026
What to learn in Structure
- Organise code into feature folders that each hold a slice
- Normalise entity collections using createEntityAdapter and selectors
- Write memoised selectors with createSelector
- Decide which state belongs in Redux and which in component state
- Avoid storing derived values that selectors can compute
Structure interview questions
Why normalise state in Redux?
Storing items by id in an object plus an array of ids avoids duplicated nested data, so one update changes one place. Lookups by id are quick and components re-render less. createEntityAdapter provides ready-made reducers and selectors for this shape.
What does createSelector do?
It builds a memoised selector from input selectors and a result function. The result is recalculated only when the inputs change by reference, so expensive derived data, like a filtered list, is not recomputed on every state change or render.
Where Structure fits in the Redux roadmap
Structure belongs to the Patterns stage (intermediate level). Scale it.
Other units in this stage
Back to the full Redux roadmap