Question

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…

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.

How are developers handling this type of requirement these days?

Answer 1

Three ways:

1. Encrypting data in cookies and sending it to client, decrypting it whenever you need it
2. Storing it server side by an Id (e.g UserId) in Cache, Session, or any other storage(which is safer than cookie).
3. Use second level caching strategy if you used an ORM