amigan_99
asked on
How to make a "load balancable" .NET application
So in my latest gig I've run into an application that seems like it was not well designed for load balancing. Let's call it FOO. FOO is a .NET application and when it was running on a single server with a connection to MS SQL the user would login to the app and then all references would be within that server. When I came on board they were having performance bottle necks so I put in simple VIP with three 443 services and it works well enough. They want the users stuck to a single server all day because "the client has to connect to multiple back end services and needs to maintain identity when going from one to the next".
At other gigs I just put in load balancing at the Citrix Netscaler or F5 or VMW NSX LB or other and I never ran into this situation where I was being asked to make the connection persistent for all day long. And the kicker is this dev team wants to be able gracefully take services out of availability which is entirely at odds with all day persistence. The Dev team doesn't seem to know how to make their app more load balancer friendly and I certainly know nothing about .NET development. So I figured out toss the question here to see if anyone can make sense of it.
What needs to happen such that a user can log in once to an application be then maintain identity and stay logged in even if the initial server they were on goes out of service?
If this question is barking mad, please be gentle!
At other gigs I just put in load balancing at the Citrix Netscaler or F5 or VMW NSX LB or other and I never ran into this situation where I was being asked to make the connection persistent for all day long. And the kicker is this dev team wants to be able gracefully take services out of availability which is entirely at odds with all day persistence. The Dev team doesn't seem to know how to make their app more load balancer friendly and I certainly know nothing about .NET development. So I figured out toss the question here to see if anyone can make sense of it.
What needs to happen such that a user can log in once to an application be then maintain identity and stay logged in even if the initial server they were on goes out of service?
If this question is barking mad, please be gentle!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.