Is Redux dead? Maybe, maybe not, but there are plenty of alternatives, Rematch being a great one.

Asayer's platform is  dedicated to providing insights and resources for developers and DevOps teams, focusing on web application monitoring, session replay, and error tracking. Through articles, tutorials, and case studies, Asayer offers insights into visualizing user sessions, reproducing bugs, and optimizing user experiences. Developers and QA engineers can learn about monitoring user interactions, detecting UI/UX issues, and improving web application performance and reliability.

asayer

Rematch is a state management library based on Redux. It builds upon a strong foundation that is Redux core while limiting the boilerplate, following Redux best practices, and providing a great development experience. Let’s take a closer look and see how it compares to Redux.

Rematch - a better Redux?

What I found when working on an Enterprise project is that the tool you are using for state-management in React is not going to work if you don’t know how to use it in a right way. The biggest problem is that Redux is not answering questions it arises. That’s why developers often store data in a global store that shouldn’t be stored there. That’s why we have Saga for async effects (and I even see new projects going with Saga not taking into account the fact that it’s not supported anymore. That’s why we have Reselect, Toolkit and other libraries to make Redux better. And that’s why we have a ton of alternatives for Redux.
And what we found with a team is that we don’t even need Redux, but we need to separate business logic (or usually state-manager logic) and our components. And React has a solution - hooks. Custom hooks became our contracts between components and logic (and this may be the logic of loading data from the backend, reading from the global state, or something else. Hooks defines an interface and under the hood it can use Redux, Remath, simple Context or whatever you want. I have <a href="https://github.com/kirillkurko/todo-react-redux-model" target="_blank" rel="noopener nofollow">MVP of the idea</a> based on the official Redux To Do example. Later I’ve been using this idea on a two more projects and we successfully moved away from a bunch of “state-management” tools to a simple and much cleaner approach

<a href="https://redux-toolkit.js.org/" target="_blank" rel="noopener nofollow">https://redux-toolkit.js.org/</a>

Worth a try after you know some Redux patterns.

my whole project replace redux with rematch from first to know how easy rematch on first release