The leading culprit of Flux store complexity is dependency management. Despite having the dispatcher as a tool to manage these dependencies, something is lost when there's too many of them. In this final section of the chapter, we'll discuss the consequences of having too many stores in our architecture and what can be done to remedy the situation.
The top-level features of our application do a decent job of providing a boundary for our stores and the state that they encapsulate. The challenge with stores is when there are too many of them. For example, as our applications grow over time, more features will be built which translates to more stores being tossed into the architecture. Additionally, the stores that already exist are apt to grow more complex as well, as they have to find ways to get along with all the other changing features of the application.
This makes for a complex scenario—growing complexity in stores and more stores overall. This...