state-management-expert

Choosing React state management requires evaluating project needs across global UI state, server state, and forms. Decision trees comparing Redux Toolkit, Zustand, Jotai, TanStack Query, and Context API guide the selection based on scalability and implementation patterns.

Use TanStack Query for server state and data fetching, while Redux Toolkit suits global UI state and complex derived state. A scalable React architecture often combines both, using TanStack Query for asynchronous server data and Redux Toolkit for client-side application state.

Managing complex form state without prop drilling is achievable using Context API for localized state or Zustand for lightweight global access. The implementation playbook recommends Zustand for its minimal boilerplate and scalable store patterns in large React applications.

Jotai works exceptionally well for derived state in large React apps via its atomic model. It handles granular state updates efficiently, preventing unnecessary re-renders, and provides a scalable alternative to Context API when global state becomes complex.

You can use Context API for global UI state in complex React applications, but it often causes performance bottlenecks due to widespread re-renders. The architecture decision tree recommends Zustand or Jotai for scalable global state to avoid these limitations.

The primary limitation of Context API for React state management is performance degradation; when context value changes, all consuming components re-render. For large applications with frequent updates, Redux Toolkit or Zustand provide optimized, scalable state architectures.