Performance Improvement: Session State
Making Decisions about Session Data
With all of the different options for doing session state and the different kinds of data that might be stored in session state how do you make an informed decision on where to store session information? The short answer is that you'll probably be leveraging several different kinds of solutions. For authentication and session information you'll likely transmit the information to the client in the form of a cookie and expect it back each time. For data like user cache you'll want to use an out of process memory cache for volume -- but smaller volumes of user cache data might have you leaving this in the same process memory. User entered data may end up encrypted and transmitted to the user and back or it might end up in a persisted store depending on the volume and sensitivity.
The key to session management is realizing that there isn't a one size fits all particularly when it comes to making the tradeoff between performance and resiliency. Some organizations may take a look at the impact of a server failure and the loss of session data and decide that it's acceptable to lose session data in the event of a server failure because they expect that a server won't fail frequently and therefore the overhead of saving session into a central place isn't warranted. Other organizations may believe that no session data can ever be lost because it's too precious.
About the Author
Robert Bogue, MS MVP Microsoft Office SharePoint Server, MCSE, MCSA:Security, etc., has contributed to more than 100 book projects and numerous other publishing projects. Robert’s latest book is The SharePoint Shepherd’s Guide for End Users. You can find out more about the book at http://www.SharePointShepherd.com. Robert blogs at http://www.thorprojects.com/blog You can reach Robert at Rob.Bogue@thorprojects.com.
Page 3 of 3