>Server 1: Management System & Database
>Server 2: Public Site
>Server 3: Public site
Use Windows network load balancing system to manage servers 2 and 3. They both run a copy of the public site code.
These sites rely heavily on sessions because they use User login, my question is:
How to keep state between servers?
The web.config of the public site currently looks like this:
Of course, this is just the case of changing “localhost” to the IP where I want to store the session? I am considering using a database server to store sessions, so it looks like this:
Is this wise?
I have found a lot of conflicting documents on this topic and hope someone can get insight into how they have/will do it.
Also (although I am here !), the management system allows you to upload images of articles. I am considering setting up a virtual directory on servers 2 and 3, which will point to the network share and map to the upload directory on the management site. Is there any reason to disagree with this?
Apologize for my ignorance, this is an uncharted territory for me!
Thank you, Sean
Usually in load balancing scenarios, you can use SQL Server sessions or ASP.NET state services.
Each has its pro/con(SQL Server The session needs to be serialized/deserialized, but keep the state if the server crashes, if the server fails over, the ASP.NET state will not keep the state, but because there is no serialization/deserialization, it will be faster).
In any case, consider hosting the service on a separate stand-alone machine-so it will not compete with other processes for resources.
The discussion about the two requires further research-just like your main The focus is on availability or speed.
Please remember that if you want to share sessions between web servers (i.e. webfarm), you need to update the machineKey settings of each server to be the same.
Here’s a good article about ASP.NET Session State (and the machineKey issue I mentioned).
We currently set up the current server for the website: < p>
>Server 1: Management System & Database
>Server 2: Public Site
>Server 3: Public Site
Use Windows Network Load Balancing System to manage the server 2 and 3. They both run a copy of the public site code.
These sites rely heavily on sessions because they use user logins. My question is:
How to keep between servers state?
The web.config of the public site currently looks like this:
Of course, this is just the case of changing “localhost” to the IP where I want to store the session? I am considering using a database server to store sessions, so it looks like this:
Is this wise?
I have found a lot of conflicting documents on this topic and hope someone can get insight into how they have/will do it.
Also (although I am here !), the management system allows you to upload images of articles. I am considering setting up a virtual directory on servers 2 and 3, which will point to the network share and map to the upload directory on the management site. Is there any reason to disagree with this?
Apologize for my ignorance, this is an uncharted territory for me!
Thank you, Sean
Depends on the country service you want.
Usually In load balancing scenarios, you can use SQL Server sessions or ASP.NET state services.
Each has its pro/con (SQL Server sessions need to be serialized/deserialized, but if the server If the server fails over, the ASP.NET state will not be maintained, but because there is no serialization/deserialization, it will be faster).
In any case, consider independent The service is hosted on the machine-so it will not compete with other processes for resources.
The discussion about the two requires further research-just as your main concern is availability or speed.
Remember, if you want to share sessions between web servers (i.e. webfarm), you need to update the machineKey settings of each server to the same.
Here’s an article about ASP.NET Session State Good article (and the machineKey issue I mentioned).