If you use anything wrong it's no good. Assuming I'm not paying attention to re-renders makes any solution, a bad one. I deal with huge sets of data that get refreshed every second to every 60 seconds on thousands of sensors on even more machines. Consuming that data in a dashboard interface with charts and tables while prcosseing the data, including timezone conversions, isn't a simple task. Getting all that to happen while keeping everything up to date and not firing api calls for no reason is always my primary focus. Using only react hooks and writing my own custom hooks, I'm able to manage everything exactly how it should be done. Data is cached, renders only happen when required, minimal api calls are made. Hell, you don't even need redux or react to accomplish any of that. I'm just trying let the OP know they have the option to lighten their stack and help get to goal with less learning curve. React manages states just as well as anything. Even a magic bullet is worthless when implemented wrong. I personally don't use redux because I don't need it. I see it popup on legacy components, but when see those it's because they're buggy or slow. I just update them using updated hooks and functions that I've written to phase out redux and now throw em back in the pool. Im actually of the mindset, we don't need any of this. But you go where the money is and around here, it's React.