Angular, N/A, React

Thoughts on Redux again

Recently I have been working on a few large scale applications where the front end is in React and the back end is using restful API’s in .NET Core 2.1. Without giving away company secrets, the applications are products that implement a platform sold to behavioral health businesses that employ clinicians and care managers to provide services to members. The services are calculated/recommended via screenings which are then calculated into scorecarsds. From there, it is determined which programs the specific members would be best suited to partake in given their condition.

Having said that, the front end has hundreds of pieces of information that need to be kept in order to determine the proper workflows to undergo from screening questionnaires to online reporting to scorecard/program analysis.

How are we able to maintain this in a “sane” manner thru React? Well it would have been a nightmare to pass props all over the place to each of the components. We only really use local component state to manage the appearance of controls in the specific component.

Enter Redux. I used Redux with success in an application using Angular2 and we’re having just as much success with it in React.

I cannot recommend enough that you explore Redux if you have not done so already and are using React and/or Angular. I cannot speak tho if Redux is suppored with Vue.js.

Leave a comment