Managing State with Redux Most

Redux-Most is a form of Redux-Observables. It also uses the concept of "epics" without requiring RXJS as a dependency. Although Redux-Observables do allow us to use other stream libraries via adapters, Redux-Most enables you to bypass needing to install both RXJS and Redux-Most. I prefer Redux-Most for working with observables and would rather have minimal dependencies.

Why use Redux-Most:

Redux-Most does not provide adapters for use with other reactive programming libraries that use the Observable type. It is simply an implementation of Redux-Observable's "Epic" pattern exclusively intended for use with Redux-Most.

How does Redux-Most work:

At first, Redux-Most provided the same API as Redux-Observables, in Which Epics get an action stream & a store middleware object containing dispatch & getState methods. It now provides both that API and another stricter, more declarative API which eliminates the use of dispatch & getState. The reason for this is that I infrequently found myself using the dispatch method. It's not really needed now, because you can use switch, merge, mergeArray, etc. to send multiple actions through your outgoing stream. This is pretty good, as it allows you to stay locked into the declarative programming style the entire time.

Where did I used Redux-Most:

Currently I am working on a project which is an E-Commerce App. I am Using Redux-Most as the state management tool and it has made my life a whole lot easier. From fetching the data through service to managing the states, It does it all! It is the ideal state management system for large Scale projects.

What is Next?

Redux-Most is arguably the Quickest, simplest, most functional, & most elegant reactive programming library in the JavaScript ecosystem right now, and Most 2.0 will be even much Better, because it will feature an auto-curried API like loadash/fp and Ramda.