{"id":239814,"date":"2016-03-28T06:29:28","date_gmt":"2016-03-28T13:29:28","guid":{"rendered":"http:\/\/css-tricks.com\/?p=239814"},"modified":"2017-04-24T07:39:18","modified_gmt":"2017-04-24T14:39:18","slug":"learning-react-redux","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/learning-react-redux\/","title":{"rendered":"Leveling Up with React: Redux"},"content":{"rendered":"
This tutorial is the final of a three-part series by Brad Westfall<\/a>. We’ll learn how to manage state across an entire application efficiently and in a way that can scale without dangerous complexity. We’ve come so far in our React journey, it’s worth making it across the finish line here and getting the full bang-for-our-buck out of this development approach.<\/em><\/p>\n <\/p>\n Redux is a tool for managing both data-state and UI-state in JavaScript applications. It’s ideal for Single Page Applications (SPAs) where managing state over time can be complex. It’s also framework-agnostic, so while it was written with React in mind, it can even be used with Angular<\/a> or a jQuery application.<\/p>\n Plus, it was conceived from an experiment with “time travel” — true fact<\/a>, we’ll get to that later!<\/p>\n As seen in our previous tutorial, React “flows” data through components<\/a>. More specifically, this is called “unidirectional data flow” — data flows in one direction from parent to child. With this characteristic, it’s not obvious how two non parent-child components would communicate in React:<\/p>\nArticle Series:<\/h4>\n
\n