Introduction

Redux is a predictable state container using to manage global state.

• It is not tied to React
  • It can be used with React, Angular, Vue or even vanilla JavaScript.
• It is a state container i.e. it stores and manages the state of the application.
• In redux, a pattern is enforced to ensure all state transitions are explicit and can be tracked so the changes to your application's state become predictable.

If you want to manage the global state of your application in a predictable way, redux can help you.

The patterns and tools provided by Redux make it easier to understand when, where, why, and how the state in your application is being updated, and how your application logic will behave when those changes occur.

Redux guides you towards writing code that is predictable and testable, which helps give you confidence that your application will work as expected.

Redux toolkit is the official, opinionated, batteries-included toolset for efficient Redux development.

• It is also intended to be the standard way to write Redux logic in your application.

Redux is great, but it does have a few shortcomings:

• Configuring redux in an app seems complicated
• Redux requires too much boilerplate code
• In addition to redux, a lot of other packages have to be installed to get redux to do something useful

Redux toolkit serves as an abstraction over redux. It hides the difficult parts ensuring you have a good developer experience.

<aside> 💡 Redux or Redux toolkit don't need a Ul library to work. React-Redux is the official Redux Ul binding library for React.

</aside>

Redux is great but not all applications need redux, as a general rule of thumb use redux when:

• You have large amounts of application state that are needed in many places in the app
• The app state is updated frequently over time and the logic to update that state may be complex