When should we be using multiple stores instead of a single store with separate slices?

[lego-sharat]

Does it depend on size of the store? Is there a rule of thumb that should be followed?

[dbritto-dev]

We follow just the AHA programming and is basically when you feel that something is getting difficult to maintain, that's the moment to start splitting your store or using slices. How can I know if I need to use multiple stores or multiple slices? well that's simple, if each part is independent from each other then multiple stores is the right path if not then multiple slices is the right path

[dai-shi]

My suggestion (as of now):

• If two things are totally isolated, multiple stores would be good.
• If they are slightly related, a single store would be good, because in the future you want an action to update both.
• For the context use case, a single store might be easier, because you need only one React Context.

[Sebastian-Nielsen]

@dai-shi @dbritto-dev
You are answers are conflicting with what's writting in the docs.

You both advocate for a single store in some situations and multiple stores in others in this discussion thread. However, on the docs page it says a single zustand store is best practice: "Although Zustand is an unopinionated library, we do recommend a few patterns. [...] Your applications global state should be located in a single Zustand store."

@dai-shi you say "If two things are totally isolated, multiple stores would be good". Okay, but would it be better than a single store with two slices, where each isolated part is stored in its own slice? If not, well then you are actually advocating for a single store.

It's confusing that the maintainer of zustand recommends something that conflicts with the docs. Is the docs just outdated or what?

[dai-shi]

Now, as we will document context usage, I think the single store would be the default and multiple stores are possible.

(Nothing is conflicting. The baseline is it's unopinionated. But, I understand it's confusing.)

[dbritto-dev]

@Sebastian-Nielsen sorry about that, we should update the docs and make clear that you shouldn't always use one global store for everything. Actually, there're multiple patterns.

By the way, I'm working on two things: update docs content and update website that will use vitepress in the new version.