Limitations of Storing the session data within web server as an In-Process data:-
1.Inspite the site is maintained in more than one webserver if the session data is stored as an InProcess data within webserver and if that server crashes then the other webserver cant read the session data and hence the response will not be provided to the client.
2. No Reliability:- Sessions will be lost when appdomain is recycled[saving web.config or restarting webserver will recycle appdomain]
To check :- open a website using sessions , execute it, now save changes on web.config while website is running ,now access the session data it will raise error because session expires due to saving changes in web.config file.
3. No Solution for Web Farming:- Web Farming is the concept of running different websites on default webservers as a one unit, this is implemented as a part of load balancing.
Browser ---------------------------------- | webserver
| ------- website1----session
|
|---- Webserver----session[new]
Website2
The single session cant be maintained for client within webfarming towards process dependent session.