title: @ngrx/effects vs simple service to http request
body: <p>When you need to add data into an application from a http request, I heard its good practice to:</p>
  
  <ol>
  <li>dispatch an action, which activates an <code>@Effect</code>.</li>
  <li><code>@Effect</code> fetches data from a <code>http</code> request.</li>
  <li>This then fires off <strong>another</strong> action</li>
  <li>Which then finally updates the store.</li>
  </ol>
  
  <p>The rationale behind this is because a http call is a side effect, and thus should be handled by the <code>@ngrx/effects</code> library.</p>
  
  <p>Is this good? I find this problematic because once the <em>first</em> action is dispatched, I have no idea if its successful or a failure. The only way I would know is if my <code>State</code> has an "hasErrorHappened" property or something similar. And I do not believe having such property is a good thing</p>
  
  <p>Or is it better to: </p>
  
  <ol>
  <li>Create a service which does the <code>http</code> call, which gets the data</li>
  <li>Update the store after the service with that data</li>
  </ol>