How to Optimize ASP.NET Core Performance with Distributed Cache? - NCache Blog - 0 views
-
alachisoft on 25 Apr 180 FACEBOOKGOOGLE PLUSTWITTERPINTERESTLINKEDINEMAIL ASP.NET Core is starting to become popular for developing web applications because of its cleaner and lighter architecture and cross platform support. And, many of these ASP.NET Core applications are high traffic and run in a load-balanced multi-server deployment. In fact, it's very common to see 10-20 server web farms and some are much larger than this. Having a multi-server load-balanced deployment makes your application-tier very scalable because you can add more servers as your transaction load increases. And, this allows your ASP.NET Core application to handle extremely large transaction loads easily. But, there is a performance bottleneck that still exists and that slows down your ASP.NET Core application. And this ASP.NET Core performance bottleneck is in your database and data storage that cannot handle heavy loads the way your ASP.NET Core application-tier can. This is because although you can add more servers to the application-tier web farm, you cannot do the same with your database tier. These are the two types of data storage that become a performance bottleneck for ASP.NET Core applications. Database Server (SQL Server) ASP.NET Core Sessions
