liveBook · Manning

State management

As explained in React in Depth

The organization, updating, and synchronization of data representing an application's current state.

State management is an architectural choice within the React ecosystem: select tools that organize application data while fitting the project’s scale, performance goals, workflow, and existing stack. section 1.4 section 1.5.4

Choose the state-management approach according to project context:

  • Use RTK in a medium-size e-commerce platform alongside Next.js, TanStack, and Material UI. section 1.5.4
  • Use Zustand in a solo portfolio project built with Vite and Tailwind CSS, where simplicity and rapid development are priorities. section 1.5.4
  • Treat Redux as a legacy constraint when maintaining an older enterprise dashboard whose stack cannot easily be refactored. section 1.5.4

Selecting a stack

A platform optimized for scalability and user experience may pair Next.js with RTK and TanStack; a portfolio may favor Vite with Zustand; an inherited dashboard may require continued Redux maintenance. section 1.5.4

How React in Depth covers it

How deep it goes
Compares library choices across project scenarios but stops short of implementation mechanics and state-update internals.
Examples
Uses RTK, Zustand, and Redux in e-commerce, portfolio, and legacy enterprise-dashboard stack scenarios.
What you can do after
Evaluate state-management libraries and choose a project-fit stack for complex React applications.
How it connects
Connects state management with React, data management, data fetching, routing, server-side rendering, styling, and performance.

Also explained in

Compare how 9 books explain state management →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of React in Depth. The section links point to the parts of the book it draws on.