Discussion on "React global state management with Context API (no Redux)"

Murat Can Yüksel · 2021-07-09T00:54:29.562Z

In my last project, I had to share state between many components. Most of them didn't share a common parent, so passing state with props and a callback function was not an option, also it would be inconvenient to do so. Therefore I used React's Conte...

I totally agree with this line *Context API is an easy and no-hassle way for developers who wish to share data between components without using a third party library like Redux.*

But sometimes it depends on the data as well that which type of data and how dynamic is the data & accordingly we should choose the 3rd party library.

Thanks

As a React newbie, which one's better? Or it depends on the situation?

Should one use the Context API or Redux?

Hello Catalin, thank you for your comment. Unfortunately, I'm a React newbie and I don't know Redux, so I can't directly answer this question.

But maybe this fact answers something at least. I also heard that Redux is a bit more complicated (which generally means can be used in more complex settings) but I don't know really.

Do you know Redux? If so, what do you think? I'll learn it next for sure, everyone is talking about it :)

It depends on the project both work really well. The Context API is probably better for medium sized projects and Redux is better for large scale projects.

Redux is a 3rd party library whereas the Context API is built in so you have to install lots of dependencies which will increase the bundle size. Also Redux has tons of boilerplate and a long setup process because you need to build the store and setup the actions from scratch.

The Context API has significantly less boilerplate so the setup is going to be quicker. However Redux has an extension for dev tools in the browser which makes it easy to see your state and the changes that are made in real time.

thanks for clarification Andrew! Andrew Baisden

Search Hashnode

React global state management with Context API (no Redux)

Responses(2)