title: What are the advantages of the ngrx/effects approach over redux-thunk?
body: <p>Im currently planning a large scale Angular 6 application, and trying to find an approach for handling side effects that is best suitable to the team needs.</p>
  
  <p>I realize that the most common way of doing it in the Ngrx ecosystem is by using the <em>ngrx/effects</em> library, and i was wondering what are the advantages of using it in comparison to <a href="https://github.com/reduxjs/redux-thunk" rel="noreferrer">thunk</a> approach, which seems to be the most popular approach for React apps.</p>
  
  <p>I get the idea of isolating all the side-effect causing logic in a single place, I always tend to isolate them under the Action Creators scope. Moving all the side effects logic to a different "abstraction layer" feels like it would add more overhead to writing a side-effect action, without considerable added value, as most of the "intense logic" actions are for handling side effects.</p>
  
  <p>Is there any other reason to favor effects over thunks? Is there any fundamental difference between ngrx in Angular and the classic Redux for React, that makes ngrx/effect a better pick?</p>