title: Angular 2+ multiple observable data services
body: <p>In my knowledge, there are 2 ways to manage application state:</p>
  
  <ul>
  <li>Flux like architecture (Redux, ngrx,...)</li>
  <li>Observable data services (<a href="http://blog.angular-university.io/how-to-build-angular2-apps-using-rxjs-observable-data-services-pitfalls-to-avoid/" rel="nofollow noreferrer">This </a> article)</li>
  </ul>
  
  <p>My app uses the second one.</p>
  
  <hr>
  
  <p>I have an <code>AuthService</code> that manage users <code>AuthState</code> (<code>id</code>, <code>accessToken</code>,...)</p>
  
  <p>Almost all other services need to access this <code>AuthState</code>. Thus, in other services, there are private fields that store this <code>AuthState</code> and I have to sync data state between them.</p>
  
  <hr>
  
  <p>Questions:</p>
  
  <ul>
  <li>Is this kind of denormalized data a normal behavior in multiple observable data services? </li>
  <li>Is centralized data store (Flux) the only way to manage state in a normalized way? If not, how should I improve my architecture?</li>
  </ul>