I have to deploy my ASP.NET application into two seperated IIS servers. My application works over HTTPS/TLS. My ASP code has to handle client SSL certificate and it means I can't use simple forward load balancers, because I will never get such certificate from nginx or Apache Load Balancer.
As I understand there is no common (open-source or free) solution for load balancing in Microsoft world and especially for SSL.
I heard about simple DNS balancing, where my domain name would be bound to several ISS servers, and every new client (session) would get IP of one server,and such way I would get simple balancing and SSL support.
Now, I am just at the begging of deployment and it is really interesting to know your opinion of such balancing, or may be to get some recommendations.
Thanks!
As for me, I can't find another solutions for HTTPS beside DNS balancing. I just have no choice.
???
Windows NLB is definitely your solution - it sits in the network stack on each of your IIS servers and distributes TCP requests among the member servers. NLB works with SSL traffic, since it distributes via TCP Ports, not the contents of the traffic.
You will need to install the same SSL certs on each server, but other then that, the configuration is trivial.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With