State Management Solutions for React Applications
mobx, react-redux, recoil, redux, redux-saga, redux-thunk, xstate, and zustand are all libraries designed to manage application state in JavaScript applications, particularly those built with React. They address the challenge of sharing, synchronizing, and updating data across components while maintaining predictability and performance. redux provides a centralized store with immutable state updates via pure reducer functions. react-redux is the official React binding for Redux, enabling efficient component subscriptions. redux-thunk and redux-saga extend Redux to handle side effects like API calls—thunks with simple async functions, sagas with generator-based control flow. mobx uses observable state and automatic reactivity to track dependencies and update components. recoil offers a graph-based model with atoms (shared state) and selectors (derived state). zustand provides a lightweight, hook-centric store with minimal boilerplate. xstate implements finite state machines and statecharts for modeling complex, deterministic workflows.
Npm Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
State Management Deep Dive: MobX, Redux Ecosystem, Recoil, Zustand, and XState Compared
Managing state in React apps goes beyond useState. When data must be shared across components, survive re-renders, or coordinate complex workflows, you need a dedicated solution. The libraries here offer different philosophies: some enforce strict immutability (redux), others embrace reactivity (mobx), while some model behavior explicitly (xstate). Let’s compare them through real engineering lenses.
🧠 Core Philosophy: How Each Library Thinks About State
redux treats state as immutable snapshots. Every change produces a new state object via pure reducer functions. This enables powerful debugging but requires discipline.
// redux: Immutable updates via reducers
const counterReducer = (state = { count: 0 }, action) => {
switch (action.type) {
case 'increment':
return { ...state, count: state.count + 1 };
default:
return state;
}
};
mobx uses observable objects. Changes to state automatically notify observers (like React components), with mutations allowed directly.
// mobx: Mutable state with automatic tracking
import { makeAutoObservable } from 'mobx';
class Counter {
count = 0;
constructor() {
makeAutoObservable(this);
}
increment() {
this.count++; // Direct mutation
}
}
recoil models state as a directed graph of atoms (units of state) and selectors (computed values). Components subscribe only to what they use.
// recoil: Atoms and selectors
import { atom, selector } from 'recoil';
const countAtom = atom({ key: 'count', default: 0 });
const doubledCount = selector({
key: 'doubledCount',
get: ({ get }) => get(countAtom) * 2
});
zustand provides a single store hook with mutable state. No providers, no actions—just a function returning state and setters.
// zustand: Minimal store
import { create } from 'zustand';
const useStore = create((set) => ({
count: 0,
increment: () => set((state) => ({ count: state.count + 1 }))
}));
xstate defines state as explicit machines with finite states and transitions. Behavior is declared upfront, preventing invalid flows.
// xstate: State machine
import { createMachine } from 'xstate';
const toggleMachine = createMachine({
id: 'toggle',
initial: 'inactive',
states: {
inactive: { on: { TOGGLE: 'active' } },
active: { on: { TOGGLE: 'inactive' } }
}
});
⚙️ Side Effects: Handling Async Logic
When your state depends on API calls or timers, how you manage side effects matters.
redux-thunk lets action creators return functions that dispatch actions asynchronously.
// redux-thunk: Simple async
const fetchUser = (id) => async (dispatch) => {
dispatch({ type: 'FETCH_START' });
try {
const user = await api.getUser(id);
dispatch({ type: 'FETCH_SUCCESS', payload: user });
} catch (err) {
dispatch({ type: 'FETCH_ERROR', error: err });
}
};
redux-saga uses generator functions to describe complex async flows declaratively.
// redux-saga: Complex async with cancellation
import { call, put, takeEvery, cancel } from 'redux-saga/effects';
function* fetchUserSaga(action) {
const task = yield fork(api.getUser, action.payload.id);
yield take('CANCEL_FETCH');
yield cancel(task);
}
function* watchFetchUser() {
yield takeEvery('FETCH_USER', fetchUserSaga);
}
mobx allows async methods directly in stores, often using async/await.
// mobx: Async in store
import { makeAutoObservable, runInAction } from 'mobx';
class UserStore {
user = null;
loading = false;
constructor() {
makeAutoObservable(this);
}
async fetchUser(id) {
this.loading = true;
try {
const user = await api.getUser(id);
runInAction(() => {
this.user = user;
this.loading = false;
});
} catch (err) {
// handle error
}
}
}
recoil supports async selectors that automatically manage loading and error states.
// recoil: Async selector
const userQuery = selector({
key: 'userQuery',
get: async ({ get }) => {
const id = get(userIdAtom);
const response = await fetch(`/api/user/${id}`);
return response.json();
}
});
zustand handles async directly in actions, similar to MobX.
// zustand: Async in store
const useStore = create((set) => ({
user: null,
loading: false,
fetchUser: async (id) => {
set({ loading: true });
try {
const user = await api.getUser(id);
set({ user, loading: false });
} catch (err) {
// handle error
}
}
}));
xstate integrates async via invoke and transition guards.
// xstate: Async in machine
const fetchUserMachine = createMachine({
id: 'fetchUser',
initial: 'idle',
context: { user: null },
states: {
idle: {
on: { FETCH: 'loading' }
},
loading: {
invoke: {
src: 'getUser',
onDone: { target: 'success', actions: 'assignUser' },
onError: 'failure'
}
},
success: {},
failure: {}
}
}, {
services: {
getUser: (context, event) => api.getUser(event.id)
},
actions: {
assignUser: assign({ user: (context, event) => event.data })
}
});
📦 Integration with React: How You Use It in Components
react-redux requires a <Provider> and uses hooks to connect components.
// react-redux: Component usage
import { useSelector, useDispatch } from 'react-redux';
function Counter() {
const count = useSelector(state => state.count);
const dispatch = useDispatch();
return (
<button onClick={() => dispatch({ type: 'increment' })}>
{count}
</button>
);
}
mobx uses observer to wrap components, which auto-track used observables.
// mobx: Observer component
import { observer } from 'mobx-react-lite';
const Counter = observer(({ store }) => (
<button onClick={() => store.increment()}>
{store.count}
</button>
));
recoil uses hooks directly—no providers needed in most cases.
// recoil: Hook usage
import { useRecoilState, useRecoilValue } from 'recoil';
function Counter() {
const [count, setCount] = useRecoilState(countAtom);
const doubled = useRecoilValue(doubledCount);
return <div>{doubled}</div>;
}
zustand uses its store hook directly in components.
// zustand: Hook usage
function Counter() {
const { count, increment } = useStore();
return <button onClick={increment}>{count}</button>;
}
xstate uses useMachine to instantiate and interact with machines.
// xstate: Hook usage
import { useMachine } from '@xstate/react';
function Toggle() {
const [state, send] = useMachine(toggleMachine);
return (
<button onClick={() => send('TOGGLE')}>
{state.value === 'active' ? 'ON' : 'OFF'}
</button>
);
}
🔍 Developer Experience: Debugging and Tooling
redux shines with the Redux DevTools extension, offering time-travel debugging, action inspection, and state diffing. Middleware like redux-logger adds console logging.
mobx offers mobx-devtools for tracking observables and reactions, though less mature than Redux’s tooling. Strict mode helps catch accidental mutations.
recoil has experimental DevTools that visualize the state graph and dependencies, but adoption is limited due to Meta’s reduced investment.
zustand provides minimal built-in tooling but integrates with Redux DevTools via middleware. Its simplicity often reduces the need for advanced debugging.
xstate includes the XState Inspector for visualizing state machines and transitions, invaluable for complex workflows.
🔄 Mutability vs Immutability: Data Update Strategies
- Immutable:
redux,react-redux,recoil(atoms are replaced, not mutated) - Mutable:
mobx,zustand(thoughzustandencourages immutable updates viaset) - Hybrid:
xstate(context can be mutable, but state transitions are immutable)
This choice affects performance, debugging, and mental model. Immutability prevents accidental side effects but requires more careful coding. Mutability feels natural but risks unexpected updates if not managed.
🧩 When to Combine Libraries
These aren’t always mutually exclusive:
- Use
redux+redux-sagafor complex enterprise apps needing audit trails. - Use
xstatefor UI workflow logic (e.g., checkout steps) alongsidezustandfor cached data. - Use
mobxfor local component state andrecoilfor global config if migrating incrementally.
Avoid mixing too many—each adds cognitive overhead.
📊 Summary Table
| Library | State Model | Async Handling | React Integration | Mutability | Best For |
|---|---|---|---|---|---|
redux | Centralized store | Middleware (thunk/saga) | react-redux | Immutable | Large apps needing strict predictability |
react-redux | Binding only | N/A | Required for Redux | N/A | Connecting Redux to React |
redux-thunk | Middleware | Simple async | With Redux | N/A | Basic API calls in Redux apps |
redux-saga | Middleware | Complex async | With Redux | N/A | Advanced async workflows in Redux |
mobx | Observable objects | Async methods | observer HOC | Mutable | Reactive apps with minimal boilerplate |
recoil | Atom graph | Async selectors | Hooks | Immutable | Fine-grained state with derived data |
zustand | Single store | Async actions | Hooks | Mutable* | Lightweight global state without providers |
xstate | State machines | Invoke/services | useMachine | Hybrid | Explicit, deterministic UI flows |
💡 Final Guidance
- Start simple: For most new apps,
zustandorrecoilreduce boilerplate without sacrificing power. - Need auditability? Stick with
reduxand its ecosystem. - Modeling complex flows?
xstateprevents bugs by design. - Prefer reactivity?
mobxfeels intuitive but requires discipline. - Avoid over-engineering: If your app only shares a few values, React Context might suffice.
Choose based on your team’s familiarity, app complexity, and long-term maintenance needs—not hype.
How to Choose: redux vs mobx vs react-redux vs recoil vs redux-saga vs redux-thunk vs xstate vs zustand
- redux:
Choose
reduxif you need a predictable, centralized state container with strong dev tools, middleware support, and time-travel debugging. It’s best suited for large applications requiring strict state immutability, auditability, and team-wide consistency. Be aware that it demands more boilerplate and learning overhead compared to newer alternatives. - mobx:
Choose
mobxif you prefer a reactive programming model where state changes automatically trigger UI updates without manual subscription management. It’s ideal for teams comfortable with mutable state and seeking to minimize boilerplate, especially in medium-to-large apps where fine-grained reactivity improves performance. However, be prepared to adopt strict mode or usemakeAutoObservableto avoid common pitfalls with observability. - react-redux:
Choose
react-reduxif you’re already using Redux and need the official, optimized React integration that handles store subscription, memoization, and context efficiently. It’s essential for any Redux-based React app, providing hooks likeuseSelectoranduseDispatch. Don’t use it standalone—it’s a binding layer, not a state management solution by itself. - recoil:
Choose
recoilif you want a modern, React-native approach to global state with built-in support for derived state, async selectors, and concurrent rendering. It works well for apps needing fine-grained updates and data-flow graphs, but note that its future is uncertain as Meta has shifted focus to React Server Components, so consider long-term maintenance risks. - redux-saga:
Choose
redux-sagaif your Redux app involves complex side effects like long-running tasks, race conditions, or cancellation logic that thunks can’t easily express. It uses ES6 generators to manage control flow declaratively, making testable and maintainable async logic. Only use it alongsideredux—it’s not a standalone state manager. - redux-thunk:
Choose
redux-thunkif your Redux app needs simple asynchronous logic like basic API calls that dispatch actions based on responses. It’s the easiest Redux middleware to learn and integrates seamlessly with standard Redux patterns. Avoid it for complex workflows involving multiple dependent async operations or cancellation—opt forredux-sagainstead. - xstate:
Choose
xstateif your application logic is best modeled as explicit state machines or statecharts, such as multi-step wizards, complex UI flows, or protocol-driven interactions. It enforces deterministic transitions and prevents invalid states, improving reliability. It’s not a general-purpose state store—use it for behavior modeling, not data caching. - zustand:
Choose
zustandif you want a minimal, hook-based global state solution with zero boilerplate, no context providers, and excellent performance out of the box. It’s perfect for small-to-medium apps or teams migrating away from Redux who still need shared state. Avoid it if you require advanced dev tools, middleware ecosystems, or strict immutability guarantees.
Popular Comparisons
README for redux
Redux is a predictable state container for JavaScript apps.
It helps you write applications that behave consistently, run in different environments (client, server, and native), and are easy to test. On top of that, it provides a great developer experience, such as live code editing combined with a time traveling debugger.
You can use Redux together with React, or with any other view library. The Redux core is tiny (2kB, including dependencies), and has a rich ecosystem of addons.
Redux Toolkit is our official recommended approach for writing Redux logic. It wraps around the Redux core, and contains packages and functions that we think are essential for building a Redux app. Redux Toolkit builds in our suggested best practices, simplifies most Redux tasks, prevents common mistakes, and makes it easier to write Redux applications.
Installation
Create a React Redux App
The recommended way to start new apps with React and Redux Toolkit is by using our official Redux Toolkit + TS template for Vite, or by creating a new Next.js project using Next's with-redux template.
Both of these already have Redux Toolkit and React-Redux configured appropriately for that build tool, and come with a small example app that demonstrates how to use several of Redux Toolkit's features.
# Vite with our Redux+TS template
# (using the `degit` tool to clone and extract the template)
npx degit reduxjs/redux-templates/packages/vite-template-redux my-app
# Next.js using the `with-redux` template
npx create-next-app --example with-redux my-app
We do not currently have official React Native templates, but recommend these templates for standard React Native and for Expo:
- https://github.com/rahsheen/react-native-template-redux-typescript
- https://github.com/rahsheen/expo-template-redux-typescript
npm install @reduxjs/toolkit react-redux
For the Redux core library by itself:
npm install redux
For more details, see the Installation docs page.
Documentation
The Redux core docs are located at https://redux.js.org, and include the full Redux tutorials, as well usage guides on general Redux patterns:
The Redux Toolkit docs are available at https://redux-toolkit.js.org, including API references and usage guides for all of the APIs included in Redux Toolkit.
Learn Redux
Redux Essentials Tutorial
The Redux Essentials tutorial is a "top-down" tutorial that teaches "how to use Redux the right way", using our latest recommended APIs and best practices. We recommend starting there.
Redux Fundamentals Tutorial
The Redux Fundamentals tutorial is a "bottom-up" tutorial that teaches "how Redux works" from first principles and without any abstractions, and why standard Redux usage patterns exist.
Help and Discussion
The #redux channel of the Reactiflux Discord community is our official resource for all questions related to learning and using Redux. Reactiflux is a great place to hang out, ask questions, and learn - please come and join us there!
Before Proceeding Further
Redux is a valuable tool for organizing your state, but you should also consider whether it's appropriate for your situation. Please don't use Redux just because someone said you should - instead, please take some time to understand the potential benefits and tradeoffs of using it.
Here are some suggestions on when it makes sense to use Redux:
- You have reasonable amounts of data changing over time
- You need a single source of truth for your state
- You find that keeping all your state in a top-level component is no longer sufficient
Yes, these guidelines are subjective and vague, but this is for a good reason. The point at which you should integrate Redux into your application is different for every user and different for every application.
For more thoughts on how Redux is meant to be used, please see:
Basic Example
The whole global state of your app is stored in an object tree inside a single store. The only way to change the state tree is to create an action, an object describing what happened, and dispatch it to the store. To specify how state gets updated in response to an action, you write pure reducer functions that calculate a new state based on the old state and the action.
Redux Toolkit simplifies the process of writing Redux logic and setting up the store. With Redux Toolkit, the basic app logic looks like:
import { createSlice, configureStore } from '@reduxjs/toolkit'
const counterSlice = createSlice({
name: 'counter',
initialState: {
value: 0
},
reducers: {
incremented: state => {
// Redux Toolkit allows us to write "mutating" logic in reducers. It
// doesn't actually mutate the state because it uses the Immer library,
// which detects changes to a "draft state" and produces a brand new
// immutable state based off those changes
state.value += 1
},
decremented: state => {
state.value -= 1
}
}
})
export const { incremented, decremented } = counterSlice.actions
const store = configureStore({
reducer: counterSlice.reducer
})
// Can still subscribe to the store
store.subscribe(() => console.log(store.getState()))
// Still pass action objects to `dispatch`, but they're created for us
store.dispatch(incremented())
// {value: 1}
store.dispatch(incremented())
// {value: 2}
store.dispatch(decremented())
// {value: 1}
Redux Toolkit allows us to write shorter logic that's easier to read, while still following the original core Redux behavior and data flow.
Logo
You can find the official logo on GitHub.
Change Log
This project adheres to Semantic Versioning. Every release, along with the migration instructions, is documented on the GitHub Releases page.