title: Application design: how much Redux state?
body: <p>I am currently working on building a small-ish app (6 front-end container-style components, 15 backend DB tables), in React. </p>
  
  <p>I'm playing around with importing Redux, and I'm having a hard time designing my application state. It seems that I'll need to store broad-based state (e.g. user sessions) into Redux, but most of the other state I'll be pulling from the backend and won't necessarily <em>need</em> it to be always up-to-date 100%.</p>
  
  <p>Based on all of the "redux-todo" style examples out there, it would seem that folks would store <em>everything</em> in their Redux store (since the state is relatively small, I suppose).</p>
  
  <p>However, for my case, I'm wondering if Redux should just be a super lightweight store for only that which needs to be persisted across the app, a la an Ember-style 'service'.</p>
  
  <p>Am I thinking about this correctly? Or should I be looking to store more state inside Redux?</p>