I've been reading a lot of resources[1][2] advocating the use of ASP.NET's Application object to store a global data cache. This limits hits to the database. However I'm skeptical of the Application object's ability to scale to larger sites with over a million page views a day. In our current web application (using just ASP), we've made it a rule not to use Application/Sessions in order to gain that tiny performance edge. Anyone have any facts/opinions regarding .NET's Application object as a data cache? Anyone have a better way?
Thanks, Monsur [1] http://www.fawcette.com/vsm/2002_04/magazine/columns/aspnet/ [2] http://www.devx.com/premier/mgznarch/vbpj/2002/02feb02/ws0202/ws0202- 1.asp You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
