React State Management: Can I Just Use Zustand Now?
I recently restarted a small project, and Redux felt like overkill, so I tried Zustand. The code is definitely shorter and more convenient, but will things be different as the project scales?
I'm curious how you combine Redux Toolkit, Zustand, or React Query in real-world projects. If you have any recommended patterns, please share them.
9 answers
For small projects, Zustand is enough, I agree. But that’s kind of a separate matter from what happens when the scale grows.
React Query and Zustand have different roles... If you split server state with Query and client global state with Zustand, they barely conflict. Just making this distinction solves half the problem.
Do you have a source? Something like a benchmark or official guide?
I've been using Zustand for 3 years in production, and I haven't really run into any issues even as the app scaled up. In fact, splitting it into slices means less boilerplate than Redux Toolkit and makes reviews easier. That said, we definitely set a rule for the team: "Don't create a store just anywhere." Without that, it's absolute hell lol.
Agreed.
I still use Redux Toolkit at work. For one reason only: I'm familiar with the DevTools and middleware ecosystem. For a new project, I'd probably go with Zustand too.
Who even uses Redux these days? Most people who say that haven’t really maintained a large-scale codebase. RTK is still widely used, and it’s a bit much to act like Zustand is unconditionally a superior replacement.
Well, I’m not so sure about that. I think it’s risky to choose it just because “the code is short and convenient.” Once you start dumping everything into a single store, Zustand can quickly turn into spaghetti too. In the end, it’s a matter of discipline, not the library—but it bothers me a bit that it’s talked about like a silver bullet...
There’s no single right answer—I think it comes down to team conventions and project lifespan. For a 6-month project, go with Zustand; if it’ll be maintained for 3+ years with multiple teams involved, consider RTK or something heavier. React Query is more of a caching layer than state management, so I’d recommend treating it as a must-have baseline.