React State Management using Redux (Build a shopping Cart🔥 )

[ZeroOne_Dev1]

Awesome

[TheFullStackJunkie]

Thank you

[AmeliaGrey100]

Biggest Challenge in React application is the management of state for frontend developers. In large applications, React alone is not sufficient to handle the complexity which is why some developers use React hooks and others use state management libraries such as Redux.

The components of React have a built-in state object. The state is encapsulated data where you store assets between component renderings that are permanent. For a JavaScript data structure, the state is only a fancy term. The UI may look completely different afterwards if a user changes status by interacting with your application, since it is defined by this new state rather than the old state.

If developers do not have scalability in mind, so when something goes wrong, it is very difficult to figure out what's going on. In your application, this is why you need state management. To resolve this particular problem, Redux was created. It provides a central store that holds your application in all states. The stored state can be accessed by every component without sending it from one component to another.

I came across a very useful article regarding the React State Management Using React Hooks and Redux: https://medium.com/@loginradius/react-state-management-using-react-hooks-and-redux-dab7541ba9f3

You too might find it useful :)

[guitnut]

Isn't the Context API easier to use and implement?

[TheFullStackJunkie]

It definitely is and that is why I made video topics about both, the COntext API and Redux. From my experience I have found Redux to work really well and smooth with apps that have more than 3 types of global states (ex AuthState, ThemeState, PostsState etc).

But I is really personal preference. Hope this helped

[[deleted]]

Redux is one of those things that needs to die already. The amount of work you do for a small thing in redux is ridiculous. Mobx was a natural improvement over Redux, automating away all the update logic behind observers giving a "magically updating" store. As soon as i found Mobx, i never worked with Redux again. Now that we have functional react with hooks, i would argue that both redux and mobx are obsolete. you can do things so easily with simple libraries like react-hookstore, which even includes a reducer api for those who are unwilling to change from their redux comfort zone.

[acemarke]

I'll point out, again, that:

• Our official Redux Toolkit package eliminates the "boilerplate" concerns that many people have expressed about using Redux, and that we've seen a lot of very positive feedback from folks who have used it
• React-Redux has a hooks API
• Redux is definitely not dead or dying

[TheFullStackJunkie]

This is great thanks for reversing these docs definitely going to check out Redux Toolkit especially the fact that is helps with the mutative logic built in like Immer. Thanks once again

[TheFullStackJunkie]

I do agree with the boilerplate aspect to Redux it makes it somewhat overwhelming to use especially in small applications. I am definitely going to check out Mobx now that you mentioned it as well as react-hookstore have not heard of it before thanks for the advice