I mapped each action type to a Subject instance.Įach stateful component will have a Subject that is then mapped into a reducer function.Īll reducer streams are combined with merge and then scan outputs the state. I just wanted to add some pragmatic differences from when I did Redux-inspired RxJS-code. To conclude, very different things for different purposes, but share some ideas. RxJS also uses the Reactive paradigm, but instead of being an architecture, it gives you basic building blocks, Observables, to accomplish this 'observing from a distance' pattern. And the Store allows others to observe its data from a distance. The Store observes actions from a distance, and changes itself. You do not set its content from a distance. Redux uses the Reactive paradigm just a little bit: the Store is reactive. In the Logger, we observe the data changes that happen in Store (from a distance), and write to the console. Here is an example of observed from a distance: // logger.js The Model is changed from the Controller. Here is an example of changed from a distance: // In the controller.js file Reactive programming is a paradigm (way of working and thinking) where data changes are observed from a distance. Think of it as an alternative to Promises. It is usually used as a tool to accomplish asynchronous tasks in JavaScript.

Think of it as an alternative to (half of) Angular. It is usually used as an architecture for UIs. Redux is a tool for managing state throughout the application. In short, they are very different libraries for very different purposes, but yes there are some vague similarities.

Rx js