• Webinars
  • Docs
  • Download
  • Blogs
  • Contact Us
Show / Hide Table of Contents
  • Programmer's Guide
  • Client Side API Programming
    • Setting Up Development Environment
    • Basic Cache Operations
      • Initialize Cache
      • Add Data to Cache
      • Update Data in Cache
      • Fetch Data From Cache
      • Remove Data From Cache
      • Dispose Cache
    • Bulk Operations
      • Adding Collection to Cache
      • Updating Collection in Cache
      • Retrieving Collection from Cache
      • Removing Collection from Cache
      • Deleting Collection from Cache
    • Asynchronous Operations
      • Using Asynchronous Operations
      • Using Asynchronous Operations with Callback Methods
    • Groups and Subgroups
      • Adding/Updating Data Group in Cache
      • Retrieving Data Group from Cache
      • Removing Data Group from Cache
    • Tagging Data in NCache
      • Creating Tags
      • Adding Items with Tags
      • Retrieving Previously Tagged Data
      • Removing Tagged Items from Cache
    • Named Tags
    • Data Expiration Strategies
      • Using Absolute Expiration
      • Using Sliding Expiration
    • Cache Dependencies
      • Key Dependency
      • File Dependency
      • Notification based Dependencies
        • Database Dependency using SQL Server
        • Database Dependency using Oracle
      • Polling Based Dependency
      • Custom Data Source Dependency
      • Multiple Cache Sync Dependency
      • Aggregate Dependency
      • Add Dependency to Existing Item
      • Using CLR Procedures to Call NCache
    • Locking Data in NCache
      • Locking Items in Cache (Pessimistic Locking)
      • Locking Items with Cache Item Versioning (Optimistic Locking)
    • SQL Reference for NCache
      • SQL Syntax
      • Querying Samples for Operators
      • Querying Data in NCache
      • NCache Language Integrated Query (LINQ)
        • Using LINQ in NCache
        • Configuring LINQPad for NCache
        • Querying NCache Data in LINQPad
    • Event Notifications
      • Cache Level Event Notifications
      • Item Level Event Notifications
      • Custom Event Notifications
    • Publish/Subscribe (Pub/Sub) in NCache
      • Pub/Sub Topics
      • Managing Topics
      • Pub/Sub Messages
        • Message Behavior and Properties
        • Creating a Message
      • Publish Messages to Topic
      • Subscribe for Topic Messages
      • Monitoring Pub/Sub Topics
    • Continuous Query
    • Using Streams in NCache
      • Opening with Stream Modes
      • Adding and Updating Data with Streams
      • Retrieving Data from Streams
      • Closing a Stream
    • Security and Encryption
      • NCache Security
      • NCache Data Encryption
    • Data Compression
    • NCache Management API
  • Server Side API Programming
    • Cache Startup Loader
      • Components of Cache Startup Loader
      • Sample Implementation of ICacheLoader on Single Node
      • Sample Implementation of ICacheLoader with Distribution Hints
    • Data Source Providers (Backing Source)
      • Read-Through Caching
        • Configure Read-Through Provider
        • Using Read-Through with Cache Operations
      • Write-Through Caching
        • Configuring Write-Through Provider
        • Using Write-Through with Basic Operations
        • Using Write-Behind with Basic Operations
        • Using Write-Behind with Bulk Operations
        • Using Write-Behind with Async Operations
        • Monitor Write-Through Counters
    • Custom Dependency
      • Sample Implementation of Custom Dependency
      • Sample Usage of Custom Dependency
    • WAN Replication through Bridge
      • Bridge Configurations
      • Implementing Bridge Conflict Resolver
    • Entry Processor
      • Sample Implementation of IEntryProcessor Interface
      • Sample Usage of EntryProcessor
    • MapReduce
      • Sample Implementation of MapReduce Interfaces
      • Sample Usage of MapReduce
    • Aggregator
      • Sample Implementation of IValueExtractor Interface
      • Sample Implementation of IAggregator Interface
      • Sample Usage of Aggregator
    • Dynamic Compact Serialization
  • Client Side ASP.NET Features
    • ASP.NET
      • ASP.NET Session State Provider for NCache
      • Multi-Region ASP.NET Session State Provider for NCache
    • ASP.NET Core
      • Session Storage in ASP.NET Core
        • Configure NCache ASP.NET Core Session Provider
        • Configure ASP.NET Core Sessions with NCache IDistributedCache Provider
      • Multi-Region ASP.NET Core Session Provider for NCache
      • Object Caching in ASP.NET Core
    • ASP.NET SignalR
      • Using NCache Extension for SignalR
    • View State Caching
      • Configuring and Using Content Optimization
      • Group View State with Sessions
      • Limit View State Caching
      • Perform Page Level Grouping for View State
    • ASP.NET Output Cache
      • Configure ASP.NET Output Caching
      • Using ASP.NET Output Cache with Custom Hooks
  • Client Side Third Party Integrations
    • Migrating AppFabric to NCache
      • AppFabric API vs. NCache API
    • NHibernate
      • NCache as NHibernate Second Level Cache
      • Using NHibernate Query Caching
      • Configuring Database Synchronization with NHibernate
    • Entity Framework Caching Integration
      • NCache as Entity Framework Second Level Cache
      • Entity Framework Caching Config File
    • Entity Framework Core Caching
      • Installing NCache Entity Framework Core Provider
      • Configuring NCache Entity Framework Core Provider
      • Using NCache Entity Framework Core Provider
        • Caching Options for EF Core Provider
        • LINQ APIs for EF Core Provider
        • Cache Only APIs for EF Core Provider
        • Query Deferred APIs for EF Core Provider
      • Logging in NCache Entity Framework Core Provider
    • Memcached
      • NCache Memcached Gateway Approach
      • Memcached Client Plugin for .NET
    • Debug NCache Providers in Visual Studio
    • NCache for Visual Studio Extension

ASP.NET Core

Note

This feature will only work with .NET Core applications targeted for .NET Framework platform.

With Microsoft restructuring ASP.NET 5 to ASP.NET Core, NCache has introduced Sessions State Management for ASP.NET Core to provide support with the new architecture. NCache provides flexible options to combine sessions with NCache’s enhanced caching capabilities, to boost performance as a whole. You can now store the default ASP.NET Core sessions within NCache or use NCache’s Session Management Services through extension methods on the ASP.NET Core modules to create and store custom configured sessions that utilize NCache.

NCache Session Properties

Exclusive Session Locking: NCache Session Management enhances ASP.NET Core Sessions by providing exclusive session locking to avoid deadlock and data integrity being compromised. Locking is configurable and by default is off.

Locking Release Retry: If an exclusive lock is used, locking retries are also configured. In case of concurrent requests, lock release is tried a configured number of times.

Location Affinity: NCache’s Session Management Services provide Location Affinity which manages ASP.NET Core Sessions across multiple web farms which 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 local region and secondary cache(s) are of distant geographical regions. These are configured in Web.config.

Cluster Topologies: For sessions, different clustering topologies offered by NCache can be used. Replicated topology offers load balancing of client so that the ASP.NET Core application does not suffer during intensive traffic. If partitioned-replicated cache is used, it provides higher scalability and reliability to the application and performs faster transactions.

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

Scalability: NCache Session uses in-memory cache as storage, where a clustered cache provides even better scalability. Working in a clustered environment allows adding more servers to session cluster at runtime; this results in more scalability and reliability for the application. Hence ASP.NET session clustering for web farms is faster and more scalable than storing them in a database.

Availability, Load Balancing, Fault Tolerance: In a web farm environment, using NCache with ASP.NET Core Sessions provides better fault tolerance, keeping session data available at all server nodes in a clustered cache. This also results handling larger load because sessions can be distributed to multiple servers in the farm.

Session Lookup in Cache Made Easy: All session data in cache can be retrieved in a single call through HttpContext.Session in ASP.NET Core.

Better Performance: Session data being stored in in-memory cache, closer to the ASP.NET application, yields maximum performance.

ASP.NET Core Components

ASP.NET Core works on the dependency injection, to allow loose coupling and more flexibility. The server is created within the application and uses the Startup class containing user-specified request handling definitions and configurations for the services. For more detail on the Startup class and its components, please refer to the ASP.NET Core documentation.

Startup.cs Components

The Startup class contains two methods:

Method Parameters Description
Configure() IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory Contains the user defined middleware logic before the logic layer is called where the session is being used. This takes care of HTTP request handling of the application. You can add middleware components to an instance of the IApplicationBuilder class to configure the request, like using MVC as a handler for the requests.
ConfigureServices() IServiceCollection services Contains the configurations for the services that are provided for HTTP request handling. Hence, this method is called before Configure(). The configuration is provided in the Appsettings.json file.

NCache provides ASP.NET Core support in two ways – you can either use NCache ASP.NET Core Session Provider instead of ASP.NET Core Sessions or use ASP.NET Core Sessions with NCache IDistributed Provider.

In This Section

Session Storage in ASP.NET Core
Explains how sessions can be stored using ASP.NET Core and NCache's enhanced features.

Multi-Region ASP.NET Core Session Provider for NCache
Explains how the location affinity feature in NCache can be configured for web farms using clustered caches distributed across multiple regions.

Object Caching in ASP.NET Core
Explains how ASP.NET Core objects can be stored using NCache.

Back to top Copyright © 2017 Alachisoft