What are the three main principles of Redux?

Redux, a popular state management library for JavaScript applications, adheres to three CORE principles that guide its design and functionality. The first principle is the concept of a single source of truth, emphasizing the importance of centralizing the application's state.

The third principle of Redux is that changes to the state are made using pure functions, known as reducers. Reducers are responsible for determining how the application's state changes in response to actions sent to the store. They take the previous state of the application and an action as arguments and return a new state object.

In this principle, the entire state of the application is encapsulated within a single object tree, residing in a single store. This approach ensures that the state is predictable and consistent, making it easier to debug and maintain the application.

The second principle of Redux is that the state is considered read-only. This means that the state cannot be modified directly. Instead, changes to the state are made through the emission of actions, which describe what happened in the application.

Actions are plain JavaScript objects that carry information from the application to the store. They describe the type of change that needs to be made and can optionally carry additional data related to that change. The store then uses this information to update the state in a predictable manner.