Popular posts

I found this diagram, I think is the most basic to understand what Redux do

You have a single store where the state of your whole application relies. One of your React components can dispatch or "trigger" an action (for example by clicking a button). Every action returns an object with a "type" property which is usually a string that serves as an identifier of the action. The reducer intercepts that action to know what to do with state on the store. The reducer do something in the state (update, add, remove, etc) and the new state of the store returns to your React components to update (if it is necessary) the interface.

The flow is always the same, it can be intimidating at first and challenging if you come from the MVC world like me but after a while you get use to it.

If you like to learn more, the Redux webiste is really good to learn the best practices in using Redux (read and understand the three principles and you're good to go). You can even learn Redux from its creator for free :)