Even though one of characteristic of Cloud is Scalable, but it does not mean all systems that are hosted in the cloud are scalable from birth. Cloud or on On-Primes won't make any different, if you we don't design it to be scallable.
Example ASP.NET Web Form
This architecture is heavily depend on Session key that pass back and forth between browser and Web server. This work great if we have only server.
But in Load Balancing scenario, where you have cluster of Web servers that share the responsibility for handling to user requests. Those requests will not always be routed to the same server. The problem came when Server A never know about session created by Server B.
But in Load Balancing scenario, where you have cluster of Web servers that share the responsibility for handling to user requests. Those requests will not always be routed to the same server. The problem came when Server A never know about session created by Server B.
Sometime people solve it by using database to manage share Session across multiple servers
This could be a solution, but is not "FUN" at all to handle all sort of VooDoo by our-self such as: Session life cycle, Concurrency access, etc... That is why Microsoft provide a support for this particular case. HOW TO: Configure SQL Server to Store ASP.NET Session State
Basically, you need to run a script to generate table and stored procedure to handle session state and add connection in Web configuration file.
My preference is try to avoid of using session completely.
Basically, you need to run a script to generate table and stored procedure to handle session state and add connection in Web configuration file.
My preference is try to avoid of using session completely.