At this point, we have a basic understanding of NgRx. We know how to set up our state and create all the artifacts that go with it such as actions, action creators, and reducers. Additionally, we have also gained familiarity with the Redux plugin for Chrome and understood what a valuable tool it can be to help us quickly gain an understanding of the state in our app, and most importantly how it can aid us in debugging any problems we may have related to NgRx.
Now, the time has come to talk about something that doesn't quite fit in to our organized and synchronous world of reducers and actions. I am talking about something called side effects. Side effects are operations such as accessing files or network resources, and is not really related to our applications state even though they may be the vessels that contain the data...
