none
Session Management RRS feed

  • Question

  • We are going to 2 Web Servers load balanced using Win 2008 R2 Load Balancer along with clustered SQL DB's [ File Storage @ SAN ].

    I need to know what should be our Session Mgmt strategy ?

    In Proc + Sticky

           (Or)

    Out Proc

    Which is good in terms of High Availability ? What are the pro's and cons of each option.

    Tuesday, July 1, 2014 11:50 AM

All replies

  • A couple of points, obviously IMO; In-Proc doesn't constrain you to sticky. Sticky is rarely a good idea. Do you need to maintain sessions at all?

    http://pauliom.wordpress.com

    Tuesday, July 1, 2014 1:52 PM
  • Hi,

    I would avoid using session state with loadbalance strategy to increase availability when the user will switch from server to server, and minimize single point of failure.

    I would prefer:
    A) Using a cookie for authentication and store information in the IIS Cache http://msdn.microsoft.com/en-us/library/vstudio/6hbbsfk6(v=vs.100).aspx
    B) Using a sticky session in order to maximize the cache efficiency and facilitate debugging

    With that, no need to setup a session manager.

    Hope it will help you

    Best regards,


    Philippe Gélinas-Bernier


    Wednesday, July 2, 2014 2:30 AM
  • Why would you recommend a sticky session? That's going to massively hurt load balancing.

    http://pauliom.wordpress.com

    Wednesday, July 2, 2014 7:49 AM
  • Hi,

    For the type of applications I’m working with, using a Class C affinity is more efficient than no affinity. If the application need to load user specific data from SQL, switching server will cause a SQL transaction.

    I agree with you on the performance issue, and I think in that case SQL requests decrease performance more than using Class C affinity.


    Like you said: VijMan do you need to maintain sessions at all, if yes what kind of information do you need to store?


    Philippe Gelinas-Bernier http://linkedin.com/in/pbernier99

    Wednesday, July 2, 2014 4:21 PM