If anyone reading this wants to learn Redux, just read the getting started guide, or watch the co-creator's video series.[1] It's wonderful. If anyone just wants a TL;DW, here's mine:
1. The state of your application should be a tree. This tree is immutable. We call it a store.
2. Each branch of your state tree is generated by a pure function of the previous state and an action. We call these reducers.
3. The only way to effect change in your state is to dispatch actions. Dispatching action X triggers the root reducer for action X (which triggers the child reducers with action X, etc.), giving you the next state.
4. Subscribe to store changes with listeners.
That's really it. A general roadmap for managing state in your software. Has nothing to do with React. Or with user interfaces. Just a general approach to software state. You can roll your own in a few minutes for your use-case. If your use case happens to be a React UI or C# app, then yeah, reach for React-Redux or Redux.NET respectively.
But please, please don't learn Redux initially by looking at a React app that uses React-Redux. That's hardcore jumping the gun.
[1] https://egghead.io/lessons/react-redux-the-single-immutable-...