Rewind for Redux Review?

This week, I have been working on a new project with React-Js and Redux and it had been a while since using Redux and I thought it would be fun to review a little bit of Redux terminology and the idea of why we want to use Redux with certain projects.

What is Redux? Redux is a library that can be used with any JavaScript framework including React, Vue, Ember, Angular, or just Vanilla JavaScript. React and Redux are often used together, but of course, they do not have to be. The UI binding to connect React and Redux libraries would be the React Redux.

Redux is a state management tool. Instead of declaring the state within the components throughout your React functions, the state for your application will all be kept in the Redux store and each component will access any state from that store as it is needed. The general idea is Redux makes the application a bit less complicated, especially for applications with a lot of components and requests.

The benefit of using a Redux library is that you can store everything in one global state in your literal store. This will allow you to simply access that state by connecting components, actions, reducers, and so on. However, even though this provides a level of ease, it also prohibits a sense of flow when it comes to organic design. You can definitely create a tidy, small, impressive, little app using Redux. However, on a larger scale, an increased layering of state manipulation logic using actions and reducers will get messy.

On the other hand, some good old fashioned organization with setState and the incorporation of the new arrival of React Hooks may make for a better choice. Still, Redux will always hold a special place in my heart and I believe it will always be valid and be around for a long time.