0

If we start to use 2 servers instead of one, with load balancing, is there a way to store sessions in memory, so we wouldn't need to change 50 webconfigs to set sessions are stored in database? Obviously, 2 servers would be there if one fails, so storing sessions in memory would back things to beginning.

Thanks.

el ninho
  • 4,183
  • 15
  • 56
  • 77
  • See http://stackoverflow.com/questions/488748/scaling-up-the-asp-net-session-state-server – NotMe Mar 16 '12 at 15:24

2 Answers2

1

One option is to use a load balancer that supports "sticky sessions". What that means is that the load balancer will always forward requests with the same session id to the same server, so no session sharing is required.

Erik Funkenbusch
  • 92,674
  • 28
  • 195
  • 291
0

If I understand your question correctly, then the answer is "No". If you are using the default inprocess session provider, then when you switch to using 2 machines, you will need to switch the session provider to some out of process (ie Sql Session provider or Memcached) session providers so that both machines can access the same session source. This means you will need to modify all the web.conf

Al W
  • 7,539
  • 1
  • 19
  • 40