title: Flux without data caching?
body: <p>Almost all examples of flux involve data cache on the client side however I don't think I would be able to do this for a lot of my application.</p>
  
  <p>In the system I am thinking about using React/Flux, a single user can have 100's of thousands of the main piece of data we store (and 1 record probably has at least 75 data properties).  Caching this much data on the client side seems like a bad idea and probably makes things more complex.</p>
  
  <p>If I were not using Flux, I would just have a ORM like system that can talk to a REST API in which case a request like <code>userRepository.getById(123)</code> would always hit the API regardless if I requested that data in the last page.  My idea is to just have the store have these methods.</p>
  
  <p>Does Flux consider it bad that if I were to make request for data, that it always hit the API and never pulls data from a local cache instance?  Can I use Flux in a way were a majority of the data retrieval requests are always going to hit an API?</p>