title: ASP.net application session cache best practices and patterns
body: <p>In asp.net the major data stores are application, session and we also have the object cache.
  I have used common sense hints/tips (e.g. never put users specific data in application, never put unmanaged resources in session etc. etc.) but to be honest I have never come across any recommendations and examples for when to use what in MSDN or from prominent figures like Haack and the Gu that cover all three together (e.g. Google's first hit to MSDN talks about using application as a global cache, if that's the case, what's the object cache for ?</p>
  
  <p>Also something that I find seldom discussed is comparison in scenario, for example I know its easy to unnecessary load up memory usage with over use of session, but what happens if you used the object cache as an alternative to store the same data ?</p>
  
  <p>Edit: This is the best information I have found so far: <a href="http://msdn.microsoft.com/en-us/library/ff647787.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ff647787.aspx</a></p>