If there is no redux:
We use the components react for Exploitation, and we will state in which each component maintenance, we will actually business logic unit of component modules split into independent from each other too, he split into components, imagine the following, if we finished the development of a project, the other one needs to be familiar with the project, while viewing a particular business logic was, he might want to see four or five have a deep understanding of the relationship between the component and each component was the principle of operation as well as other components, can finally understand it was going to developers is how to handle this business logic too, so there will be any problems then? That is, if we just want to simply have a certain understanding of the business logic, we do not want mixed with unnecessary things in this process have to understand, such as the front: we must understand the inner workings of the components, it is clearly unnecessary.
With After redux:
We put business logic state separate out the maintenance and design of strict action and reducer to handle the flow define business logic, so when someone else took over the fact that he only need to focus redux business logic in dealing with business logic just fine, except when he was revised interface need to understand the components while the business logic layer also pulled out of view in favor of division of labor.