manpreet Best Answer 3 years ago

I have seen different strategies for splitting redux store into slices (each slice having a state, reducers, actions and actionCreators) and I am wondering what the pros and cons of each strategy is.

Split based on backend Resources

In the restful world, backend models are named resources. Since the front-end let the user interact with objects of these classes, therefore we may have redux slices specific to each resource.

Example: A slice for resource Post with a state consisting of keys such as posts, selectedPost, etc.

Split based on frontend sub-modules

If you think of sub-modules as independent partitions of your app, each needs its own namespace in the rootStore.

Example: A slice for profile, settings, and dashboard sub-modules

Split by application pages (or Routes)

Each page with route, has its own slice.

Example: User-Settings page, Organization-Settings page, Notifications-Settings page, Main-Settings page

Also I was wondering if there was other strategies I do not know about.