REDUX

Redux is a container for storing states that facilitates organization between application components. When there are too many components, data, and connections between them in a project, you need to structure them and make them more predictable. Otherwise, developers will no longer understand what their code does and where. This is why they use Redux, an event system based on Flux architecture. Now that all states are stored in one place, you can make sure that changes in one of the components are notified to others who need to know about them. And they get this information from the redux container after the data about changes in the first component gets there. In this case, redux, as a storage, protects the system from errors that occur if you do not control the transfer of states.

In practice, despite the simple logic, Redux is a much more complex system, and it is not suitable for all projects. In order to use this library effectively, an application must store its state in local storage, fill it in on the server, pass it to the client as HTML, and meet several other technical nuances. All you have to do is trust the architect who will tell you that the best solution for your application tasks is to use redux. However, it's not always necessary - you can replace it with simpler, more technically sound, and universal off-the-shelf solutions or write a unique module that will do the same thing, but in accordance with the logic of your project.

Although the logic behind Redux is quite simple, and the library itself will take up about two megabytes of memory allocated to the application, it is not necessary to use this storage. Simple applications that don't manage server-side events don't need it, but it will be very difficult to create a complex and large-scale React project without it. Using Redux will make the system more stable and reliable, and most importantly, it will greatly facilitate the scaling of a web application.