We are excited to announce the release of NCache 4.6 Service Pack 2. This service pack has had client cache optimizations, enhancements in bridge topology and upgrades in features related to cache monitoring. This is a recommended upgrade for all existing users. You may find the release notes for this release here. Additionally, the key highlights of this release are below.
Optimized Client Cache
We made several changes to the way a client cache is used to synchronize with a clustered cache. In this latest release, the synchronization happens in an optimized way. Previously, the issue was that for each update made to a clustered cache, the client cache had to receive events. But now in NCache 4.6 SP2, we have fixed this and the client cache can now receive events in bulk at configurable intervals. This reduces the traffic as well as memory usage.
Along with an optimized client cache, we have introduced a new API for monitoring cache clients. You can use the new API to monitor cache clients connected with a cluster, to fetch a list of connected clients and to define notification triggers in case any new clients connect or existing clients disconnect.
Learn more in the Release Notes here.
Distributed Cache Loader
Startup Cache Loader helped our users to preload data in a cache when it starts up. However, this was a slow operation as it used to happen in a single node. The NCache 4.6 SP2 release helps you to use a Cache Loader in a distributed manner. Meaning the NCache startup cache loader can now run on multiple nodes which can help in faster cache loading.
To configure a Cache Startup Loader, the ICacheLoader interface needs to be implemented and then configured using NCache Web Manager. NCache uses this custom provider to load data from the configured data source either in bulk or sequentially depending on the key dependency among the items. Learn More about Cache Startup Loader and how to use it.
FIPS Compliant AES Encryption
We value the security of our customer data residing in the cache. To strengthen the security of the cache further, NCache is pleased to add a FIPS compliant AES encryption feature with 4.6 SP2. This will help you to ensure that your cache is protected from unauthorized access and that transmissions between your application and cache servers happen in a secure way.
Interestingly, you can do all of this without any code changes or rip and replace. Various other encryption options are also available. The Federal Information Processing Standard is an industry requirement recommended by the US government for implementing software security. You can do 3DES (168-bit), AES-128, AES-192 or AES 256 encryptions of your cache. Learn more about NCache’s Security & Encryption Features here.
ASP.NET Core Session Provider
NCache 4.6 SP2 now supports ASP.NET Session Storage Provider for ASP.NET Core applications. Learn more about how to configure ASP.NET Core Session Provider for NCache and our support for multi-regions ASP.NET core sessions here.
Changes in Licensing
We made various changes in NCache 4.6 SP2 to support new licensing. The main change is that NCache is now licensed based on the number of cores a machine has. For every 4 cores, 1 license is used. Developer licensed machines can now connect to a remote cache but with limitations on the number of requests per second and a total number of requests a client can be made to remote cache. Get in touch with our Solution Architects for detailed demo sessions and customized quotes for your architecture. You can book a personalized demo here.
Get Started with NCache?
You can start evaluating a free 60-day trial for the latest NCache 4.6 SP2 release and try the latest and most stable release of NCache to help you build highly scalable and performance optimized .NET applications.