title: Persisting user data in MVC 3
body: <p>I have been given a requirement to persist user data once the user has authenticated initially. We don't want to hit the database to look up the user every time they navigate to a new view etc...</p>
  
  <p>I have a User class that is [Serializable] so it could be stored in a session. I am using SQL server for session state as well. I was thinking of storing the object in session but I really hate doing that.</p>
  
  <p>How are developers handling this type of requirement these days?</p>