Discussion on "Should I totally ditch redux API for context API?"

Adedipe Oluwatobi · 2021-04-05T08:54:48.093Z

Introduction If you're like me, immediately you learned how to use react hooks and the context API (useContext) you'd have stopped using redux for your app(web/mobile) state management. But, the challenges I faced this week at work thought me otherw...

Nice piece, actually most developers needs to read this before saying redux is too complex

Hi Adedipe,

If you want to try a new tool for your projects you can check our Saas plateform which facilitate integration of APIS.

We tend to simplify the integration of APIs, the interfaces that allow the exchange between isolated services and data.

meta-api.io

You can reach me if you have questions !

Salim

Hello , may you tell more about when to use redux and when to use Context...means the use cases , how to differentiate between them. Thank you

useContext can be used when your app isn't very complex, for example if you want to use a variable in multiple files, and you know that the value of that variable is going to be the same across those files. You can add useReducer if you need to have a moderately complex state management in your app, for example if you're fetching some data from an external API and you want to be able to manage how you dispatch actions. Redux would work better if, your app state is updated frequently, logic to update the state is complex. etc.

this blog post goes into further details

blog.isquaredsoftware.com/2021/01/context-redux-d…

Adedipe Oluwatobi Thanks , but i like context as i only know this ,,, : )

Vipin Gautam Haha, you're welcome. I actually love context, its easier to understand. A use case i think i mentioned in the post is if you want to update or use your state outside of a functional component, context doesn't really work for that.

Agreed they both serve a purpose and its convenient switching between the two.

Search Hashnode

Should I totally ditch redux API for context API?

Responses4