Chapter 1. Introducing Redux


This chapter covers

  • Defining Redux
  • Understanding the differences between Flux and Redux
  • Using Redux with React
  • Introducing actions, reducers, and the store
  • Learning when to use Redux

If you hop into any React web application in 2018, there’s a good chance you’ll find Redux there to manage its state. It’s remarkable that we reached this place so quickly, though. A few years ago, Redux had yet to be created and React enjoyed an excited and blossoming user base. Early adopters of React believed that they’d found the best solution yet to the view layer—the “V” of the MVC (Model-View-Controller) front-end framework puzzle. What they couldn’t agree on was how to manage the state of those applications once they became the size and complexity that the real world demands. Eventually, Redux settled the debate.

Throughout the course of this book, we’ll explore Redux and its ecosystem through the lens of a React application. As you’ll learn, Redux can be plugged into JavaScript applications of all flavors, but React is an ideal playground for a few reasons. Chief among those reasons: Redux was created in the context of React. You’re most likely to encounter Redux within a React application, and React is agnostic about how you manage the data layer of your application. Without further ado, let’s jump in.

1.1. What is state?

1.2. What is Flux?

1.3. What is Redux?

1.4. Why should I use Redux?

1.5. When should I use Redux?

1.6. Alternatives to Redux