+Modern State Management Is a Problem of State Partitioning
State management in modern frontend development is not simply about storing variables. It is about identifying what kinds of state exist in an application and deciding, for each one, its authoritative owner, scope of use, lifetime, and synchronization rules.[Footnote 18]
The Redux documentation explicitly notes that not all state needs to live in a global store, and that developers must decide where each piece of state belongs. React likewise associates state with a position in the component tree, recommends lifting shared state to the nearest common owner, and advises against separately storing duplicated or derivable state.
Server state differs fundamentally from local UI state. Its source of truth is owned by a remote system, while the client must cache it, refetch it, invalidate it, and deal with stale data. If component state and server state are placed in the same global object and managed under identical lifetime rules, their actual ownership and behavioral contracts can become obscured.[Footnote 19]
