Have Geek Brain

Load Balancing OR Failover Servers for .net Application

Scenario I have a service written in C # .net.

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

So, for example, if one server dies, the service continues to run on the other server and users are not affected. Or, if the site has a large download, users are redirected to different servers.

For users being redirected to different servers, no problem, we have software that can check if the service is running or not. How to do session management in this case?

How can we achieve this?

+1


source to share


2 answers


Of course, you can always spin up your own session management service, but I don't think that's what you are looking for.

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



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

0


source


Very old question, but Google is still searchable. Since Windows 2012 there is a Clustered Shared Tasks feature. Probably not ripe yet since it is only managed through PowerShell, but it might be a good place to start. Check the MSDN post . I really want to try.



0


source






More articles:


All Articles