Today’s ASP.NET / ASP.NET Core web applications, .NET Web Services, .NET Microservices, and any other .NET server applications need to handle extreme transaction loads. And, they need to use a distributed cache to achieve this goal because data storage and databases quickly become a bottleneck. A distributed cache allows you to cache data and reduce those expensive database trips.
Over the last 13 years since 2005, NCache has provided such capabilities for .NET applications. NCache is a popular Open Source (Apache 2.0 License) distributed cache for .NET. NCache is 100% .NET / .NET Core and allows you to cache application data as well as ASP.NET / ASP.NET Sessions, ASP.NET Core Response Cache, ASP.NET View State, and more.
Redis has been around since 2009 positioning itself as an Open Source (BSD License) key-value store with persistence. Redis has mainly been on the Linux platform and used by applications developed in PHP, Python, Java, and other similar languages. Redis was unknown to the .NET community until 2012 when Microsoft decided to use it in Azure when they decided to discontinue their own offering of AppFabric.
Learn how NCache compares with Redis for your .NET applications scaling needs. NCache is .NET native with self-healing cluster capabilities and has various improvements over Redis for .NET applications. In this whitepaper, our key focus is on areas where Redis and NCache are different to help you with your evaluation.