Received same action(s) within redux
will be executed first and then one(s) in epic(s) of redux-observable
if there are common action(s) existing in redux
and redux-observable
.[1]
Figure 1. Excerpt statement from redux-observable official site
[2] Figure 2. Order sequence diagram for redux-observable. Photo credit to Brian Leathem [3]
Redux
store is action-in and state-out. Redux-observable
is action-in and action-out.
Behavior of redux
means it generate out new centralize-management state tree depending on receiving action’s type. Behavior of redux-observable
means it generate out new action depending on receiving action’s type. Benefits of redux-observable
are describe below:
takeUntil
if sending API request and dealing with exception as using rxjs
.redux
are interested in, for generating new state tree so redux-observable
can focus on how to handle side-effects.Reference: