This repository contains a set of samples that shows how Redux-Observable and RxJS can help you to take a reactive approach when buiding React applications. This not only helps in providing a better overall design (as it makes separation of concerns easier), but also improves other ways of managing async code in Redux.
You can watch an introduction to the reactive approach to Redux in these two presentations from Ben Lesh and Jay Phelps, both from Netflix.
You can take an introduction to Reactive Programming by reading this awesome article by Andre Staltz and also watching this short video.
Redux-thunk is the de facto middleware used for managing asynchronous logic in Redux. However, as you start adding multiple concerns into an action, your logic becomes difficult to follow, mantain and reason about. You then might think on decoupling concerns that need to be kicked off at a moment in time. Meaning, you would want to embrace event sourcing (reactive style) over command pattern (imperative style). In this sample, quantity does not instruct anything in regards to price, because it is not its concern. However, price reacts to changes in quantity.
What also makes redux-observable so interesting is the ability to handle asynchronous functions. In these samples we use the mergeMap, catchError and race operators to enable error management and async code cancellation, which is not possible using Redux-thunk. The samples also demonstrate that using Redux-observable you easily get rid of the callback-hell introduced by Redux-thunk.
RxJs provide tens of operators. This sample plays with scan and buffer. It also makes use of the state$ stream to access the state from an epic.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.