redux-toolkit VS react-clean-architecture

Redux Toolkit offers a robust and predictable framework that scales well with large applications.

Redux Toolkit Official Docs

8. Redux & Redux Toolkit – State Management Simplified 🧠

Redux is a predictable state management tool for JavaScript apps. A state is something that keeps the app running for example when you are asked to select gender in a website, the state is either male or female.

I said the wrong shape, because I think that, if redux-toolkit was the version people used a lot in the past, their views on redux would be different today. Being more positive, than it is.

So you can imagine how much more we'd need to write to introduce reducers and actions in a real-world application. This is where Redux ToolKit comes in very handy.

Redux Toolkit Documentation

Redux is rather overkill in today's front end ecosystem if you're building an MVP, and as of late more have been using redux-toolkit or useReducer to update slices of state.4

React 19 Async Features Boa v0.20 Rust-Powered Engine Safari 18.2 Developer Updates Redux Toolkit 2.5 Termo Civet Rockpack

RTK Query: A data-fetching and state management tool for making API requests to our backend.

I was also looking for similar resources. We ended up adapting ideas from clean architecture (https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html) in our app. A good starting point for me was this repo with an example implementation: https://github.com/eduardomoroni/react-clean-architecture

React Implementation

I know there is clean architecture. But I am wondering what other ways are there to architect large React web front-ends with Redux. How the project structure would look like?