References — fw-01 mini-redux, and Reading an Entire Production Library
Primary sources first. Read the real implementation after you have written yours, never before.
The library itself
- redux/src — small enough to read completely in an afternoon, which is exactly why it is the first source-reading exercise. Start with
createStore.tsandcombineReducers.ts. applyMiddleware.ts— the function-composition trick worth understanding properly- Redux Toolkit — what the ecosystem actually uses now, and why the original API needed wrapping
Design background
- Dan Abramov — Redux: the first 30 seconds and the three principles
- Flux architecture — the predecessor Redux compressed into one store
- Elm architecture — where the model/update/view loop came from
- Dan Abramov — You Might Not Need Redux — by the author; the honest cost accounting
Alternatives worth comparing
- Zustand — the same problem with far less ceremony
- Jotai · Valtio — atom-based and proxy-based takes
- XState — when the state is genuinely a machine
Related modules
- fw-03 — Reactivity & signals — the alternative answer to the same question
- fw-09 — Query cache — why server state does not belong in a Redux store
- fe-15/fe-16 — State taxonomy & server state (planned) — the architectural counterpart
When a claim here proves stale, record it in PROGRESS.md section 7.