title: Confused about React's Flux architecture - waitFor
body: <p>I have my own opiniated way on how to use React and am building my own framework, inspired by Om. I am implementing something a bit similar to the Flux architecture, with stores that can update themselves on some events.</p>
  
  <p>What I am not sure to understand is why in the Flux architecture do we need store dependencies?</p>
  
  <p>Stores aren't supposed to be self-contained data holders for a given bounded context, like we do with CQRS architectures? </p>
  
  <p>In an evented system, 2 CQRS components could end up holding the same data. Do we express store dependencies to avoid holding duplicate data in stores? </p>
  
  <p>Can someone come up with some very concrete use cases where store dependencies are needed and where the problem can hardly be solved in any other way? I can't find any myself.</p>