Basic React/Redux flow

This may initially seem like an overly complex or confusing way to manage your app. But no matter how many pieces you decide to add later on, it will all still fit into the same architecture.

With React, the big draw is that you can take a bunch of different javascript objects & combine them all into 1. It turns out, this can make things easier. Here’s how..

A Provider

This makes the 1 big Javascript object, or (the store) available to be piped down to all the containers.


These are the glue that connect your React components with your Redux store. They will retrieve the apps data from the store and then send it to the components to further specify how the data should be displayed.


The components will instruct the containers on how to display the data. Whenever the applications state changes in the store,the new data is piped down & the components are automatically re-rendered.


They are any changes made to the applications state. More specifically, there’s two parts. The action creator and the action itself. The action creator houses the action, which is basically its return statement. The return statement consists of an object with a type and a payload.


They are functions that mirror the actions a user can make inside an application. When an action is made, Reducers will inform the store on which pieces of the applications state must change/be updated.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.