We use SQL Server for our application session session. Since SQL Server is a point of failure, when it's a problem, it can affect all our customers. To reduce this problem, we plan to create a SQL 2012 high-availability example and manage the Net session on our own servers. Problems with a node when the instance of SQL 2012 high availability may fail automatically or manually. We are planning to use VPRian to solve state data of the session in these lightweight ASPState examples. Instead of using the WarriPion to pile. Session session data at the webserver level, is there an approach to shaping an optional application level, which we can consider? This is a common enough problem for high traffic ASP.NET sites that use Net session management.
Comments
Post a Comment