ASP.NET Caching Benefits and Overview

You can use NCache's clustered sessions in your existing ASP.NET applications without any major code changes and can immediately see a boost in your application performance. NCache provides high-performance in-memory ASP.NET Session clustering for web farms that is faster and more scalable than storing them in a database. It is faster because sessions are kept in-memory and closer to the ASP.NET application. It is also more scalable because sessions can be distributed to multiple servers in the farm to better handle larger loads than a database server.

With NCache, you can eliminate the need for sticky sessions in your Load Balancer. This significantly improves your application's scalability. Moreover, NCache provides powerful dynamic session clustering. You can replicate or distribute sessions either locally on multiple web servers or multiple dedicated session caching servers. NCache offers a rich set of features to grow your session clustering from small to large web farms.

ASP.NET Session-State allows storing session data into a custom data source by implementing the SessionStateStoreProviderBase class. A Session-State Store Provider has been implemented using NCache to store data in a distributed cache.

NCache-based Session-State Store Provider has the following benefits:

  • No Code Change: NCache Session-State Provider can be used in an application without any code change.

  • Better Performance: Session data is stored in an in-memory cache that yields maximum performance.

  • Reliability: By default, the session is stored in the memory of the ASP.NET process. If the process recycles or the application server goes down, session data is lost. With NCache, session data is stored, outside of the ASP.NET process, in the cache cluster. Any cache topology can be opted to meet the needs of reliability. So, in case the application server goes down, session data remains available when the ASP.NET process recycles or the application server comes back.

  • No Need of Sticky Sessions: NCache Session-State Provider eliminates the use of sticky sessions in the Load Balancer.

  • NCache Cache Storage-Scalability: NCache Session-State Provider uses NCache for storage. More servers can be added to the session cluster at runtime, allowing better scalability and reliability for the application. ASP.NET session clustering for web farms is faster and more scalable than storing them in a database.

  • Availability, Load Balancing, and Fault Tolerance: In a web farm environment, NCache session clusters handle larger loads more effectively by keeping session data available at all server nodes in the cluster cache, providing better fault tolerance. This is because sessions can be distributed to multiple servers on the farm. Thus, it is safe to say that it results in high performance. It is suitable for session clustering from small to large web farms.

  • Cluster Topologies: For session cache, different clustering topologies can be used. Replicated topology offers load balancing of clients so that the web application does not suffer during intensive traffic. If a Partition-Replica cache is used, it gives high scalability and reliability to the application, and is extremely fast. Sessions can be replicated or distributed/partitioned either locally on multiple web servers or multiple dedicated session caching servers. For cache topology details, see section Cache Topologies.

  • Session Lookup in Cache Made Easy: All session data in the cache can be retrieved in a single call. NCache provides a tag with the session. In one single operation, all session data with a tag can be easily fetched.

  • Exclusive Locking: To avoid deadlock and data integrity issues, exclusive locks are provided in NCache Session-State Provider. Locking is configurable and by default, it is disabled.

  • Locking Release Retry: If an exclusive lock is used, locking retries are also configured. In case of concurrent requests, the lock can be released.

  • Location Affinity: NCache’s Session-State Provider's Location Affinity manages ASP.NET Session-State across multiple web farms that are geographically separated. For Location Affinity, one 'primary' and one or more 'secondary' caches have to be specified for each web farm. The primary cache will be used for all local traffic in the local region, and the secondary cache(s) are of distant geographical regions. These are configured in the application's Web.config file.

In This Section

ASP.NET Session-State Provider Properties
Explains how Sessions can be stored using NCache's Session-State Provider for ASP.NET.

Multi-Region ASP.NET Session-State Provider Configuration
Explains how the Location Affinity feature in NCache can be configured for web farms using clustered caches distributed across multiple regions.

Session Sharing between ASP.NET and ASP.NET Core
Explains how ASP.NET Sessions can be shared and updated with ASP.NET Core Sessions and vice versa.

ASP.NET SignalR Backplane
Explains how to configure and utilize SignalR using NCache in ASP.NET applications.

ASP.NET View State Caching
Explains how to use View State Caching and the content optimization feature of NCache.

Distributed Cache for ASP.NET Output Caching
Shows how to use Output Caching to cache the HTML output of dynamic requests to ASP.NET pages, hence speeding up the overall response process.