1

Scenario I have service written in c#.net.

Now on my production environment I want this service to be on 2 different servers for Loadbalancing or failover of one of the server.

So for instance if one server dies the service keeps running on the other server and users are not affected OR if there is a heavy load on the site users get redirected to different servers.

For users getting on redirected on different servers is not a problem we have the software which can check whether the service is running or not. How to do session management in this case?

How can we achieve this?

Dominic Rodger
  • 97,747
  • 36
  • 197
  • 212
Miral
  • 5,968
  • 16
  • 57
  • 85

2 Answers2

0

Of course you could always spin your own session management service but I don't think that is what you are looking for.

I have experience using NCache for session management and it works well enough.

Microsoft also has Velocity but I'm not sure it's complete yet.

Cory Charlton
  • 8,868
  • 4
  • 48
  • 68
0

Very old question, but still searchable by Google. Since Windows 2012 there is feature called Clustered Shared Tasks. Probably not mature yet as it is manageble only via PowerShell, but maybe good start. Check this MSDN post. I'm eager to try it myself.

Jan Zahradník
  • 2,417
  • 2
  • 33
  • 44