In Redux (React Flux implementation) guide https://redux.js.org/basics/reducers it is said, that
In Redux, all the application state is stored as a single object
My questions are:
- How seriously we should take this principle? E.g. my application can have multiple entities like Person, Invoice+InvoiceLine, Article, etc - full set entities for traditional ERP application. Each entity is handled by separate form inside SPA application. Doe we really need to store each active entity (each invoice under editing) in single central Redux store and access its properties inside InvoiceComponent, ArticleComponen as this.props.... objects? Or maybe it is better to load those enties into this.state objects (using Redux store as temporary store where objects sit during time between retrieval from backend till going to the components) and uses central store for application wide configuration parameters (e.g. logges user data, preferences, etc.)?
- If we should put almost everything into Redux store, how this impact the possible limits of application and possible performance of application. What is diferrence between Redux store and the God's class?
Maybe SPA is just not appropriate for the frontend of ERP type applications whose characteristic is the huge schema of interrelated entities?