React state management: Is zustand still the answer in 2025?

As my side project has grown a bit, I'm trying to rethink how we handle state management. We've been using zustand so far, but someone who recently joined the team wants us to go back to Redux Toolkit.

Here's how I see the characteristics of each library:

  • zustand: Less boilerplate and a low learning curve. However, at a large scale, the store can get messy if there aren't clear rules.
  • RTK: It has established patterns, which is an advantage for collaboration. On the other hand, the amount of code increases significantly.
  • Jotai: The atomic model is elegant, but team members find it confusing at first.

In the end, it seems to come down to team size and preferences. Where do you all compromise? I'd love to hear from people who have used these in production for a long time.

by 디지털노마드455

3 answers

I tried Jotai, and at first everyone gets confused, but after a month they actually find it the most convenient lol. The first hurdle is convincing the team, though... That's true.

by 궁금한사람851 · ▲0

I had similar concerns, but I ended up going with "what most of the team already knows." I found that avoiding "why did you write it this way?" in reviews is much more important than pretty code. That said, if you keep zustand, just setting a rule to split files by store slice is enough to handle large-scale projects. Make a document for action naming conventions.

by 무한도전러774 · ▲0

Hmm, I'm not so sure. Reintroducing RTK into a side project feels a bit excessive... It seems like the person who joined the team just wants something they're familiar with, rather than it being about collaboration—wouldn't you say? Ask them first for evidence of how much RTK patterns actually improve collaboration. To me, it just looks like avoiding the learning curve.

by 문과출신개발자378 · ▲0