We have an ASP.Net MVC project that starts with a single web server, but is likely to scale soon in a small web farm. Since ASP.Net authentication stores the user ID, and caching data can also be useful, we will most likely need to quickly switch to the public server.
I would like to hear from others how State Server should work and how it scales in terms of performance.
Alternatively, we could archive it as completely standstill without using data caching and tracking sessions with an encrypted cookie.
Update: I had some misinformation earlier (from Microsoft Technical Advisor ...), Auth does not store the session, as I thought it was just stored in a cookie. Thus, in this situation, we do not need a state server.
source
share