NCache 5.2 Released

The NCache team is happy to announce the release of NCache 5.2. The latest release now has a web-based GUI tool for NCache management and basic monitoring. NCache Web Manager allows users to create, configure, start and stop caches. Apart from other improvements, two additional enhancements are made to Pub/Sub which includes the priority of TOPIC and ordered delivery of messages.

To learn more about the changes and improvements in NCache 5.2, you can read our release notes here.
NCache Release Notes 5.2

What to expect in the NCache 5.2 Release:
Here are the details of all the new key features in NCache 5.2:

1. Cache Refresher
   Cache Loader/Refresher is a service that runs periodically at a configurable interval and refreshes cache data. Users configure this feature by adding one or more named datasets in configuration. Each dataset can be configured to be either loaded one time or refreshed periodically.
2. TOPIC (Pub/Sub) Enhancements
   The following two additions are made to Pub/Sub.
   • • Priority of TOPIC
       At the time of creation of a TOPIC, a priority can be assigned to a TOPIC. Messages from the higher priority TOPICs are delivered first while messages from the lower priority TOPICs are evicted first. If priority is not assigned, a TOPIC is created with ‘Normal’ priority.
     • Ordered Delivery
       Publisher should be able to send messages with instructions to preserve the order in which they are published. Such messages are delivered to subscribers in the exact same order as they were published with. Ordered messages from a certain publisher will reside on one cache server. This will be implemented using location affinity.
       All ordered messages will be delivered to the same subscriber in case of DeliveryOption.Any.
3. Query Indexes from JSON Documents
   For applications purely using JSON API, defining .NET or Java based query indexes may not be possible. Therefore, definitions of indexes from JSON documents is supported.In this case, the user specifies the path to a JSON file. NCache Web Manager reads the attributes in JSON file and list them in a grid. Users can select one or more attributes from the list for which indexes should be defined.Query indexes from JSON documents can also be created using PowerShell commands.
4. Custom Dependency Provider
   Custom dependency is now deployed on the server side. Just like Read/Write Thru providers, users need to implement Custom Dependency providers. There can be one or more custom dependency providers and each will have a unique name.When adding an item through API, the user specifies the name of custom dependency providers already configured and deployed.
5. Templates for Email Notifications
   Users may want to change the text and subjects of email notifications they receive from NCache. All the text and subjects of emails that are generated by NCache use templates. These templates are shipped inside the install directory. Users can change these templates according to their requirements.
6. Support for Two LDAP Controllers
   In some organizations, there may be more than one domain controller configured for high availability. When a primary domain controller goes down, the secondary controller becomes active. NCache now also supports configuring security with both primary and secondary domain controllers.
7. TLS for Linux
   TLS 1.2 support is provided for transport level communications between NCache servers on Linux and cache clients.
8. Session Sharing between ASP.NET and ASP.NET Core
   Sharing sessions between ASP.NET and ASP.NET Core applications is supported. This can be enabled from configuration settings. For sharing sessions between different applications, all applications must use the same custom session id generator.This is also supported for multi-regional sessions.Session sharing is not supported if configured through IDistributedCache.
9. Dependencies Support in Response Cache
   Users can specify SQL dependencies to invalidate the response of a page from cache. If the data corresponding to the SQL specified gets modified or deleted, the response of the cache gets deleted. On the new requests, it gets regenerated and is added to the cache with the same SQL dependency.This is not supported if configured through IDistributedCache.
10. Identity Server 4
    NCache can be used as an external store for Identity Server 4 as;
    • • A caching layer on top of Identity Server 4 store.
      • A persistence store for Identity Server 4.
11. Support for Multiple Caches through IDistributedCache
    When configured with NCache, users may want to use different caches like session caching and data caching. NCache provides an option to use multiple caches for different purposes when used as IDistributedCache.
12. New Java Client
    The new Java client is 100% identical to the new .NET API. It has the following services:
    • • Search Service
      • Messaging Service
      • Notification Service
13. Java based Server-side Code
    The following server-side modules can be written in Java.
14. New Node.js Client
    NCache now has a Node.js client which is 100% identical to the new .NET & Java JSON API. It has the following services;
15. Prometheus
    Integration with Prometheus for monitoring key metrics of NCache. NCache publishes a configurable set of counters to Prometheus servers.
16. Grafana
    An NCache dashboard for Grafana is provided on Grafana gallery. The dashboard has various counters that are fetched from Prometheus servers where NCache is publishing its counters.
17. NCache Web Manager in Professional Edition
    NCache Professional edition now has a web-based GUI tool for NCache management and basic monitoring. NCache Web Manager allows users to create, configure, start and stop caches. This also helps them quickly run a stress test and see statistics.

The new Java client also uses pipelining for better performance.

Get Started with NCache 5.2

You can start evaluating a free 60-day trial for the latest NCache 5.2 release with the latest features of NCache Enterprise that can help you build highly scalable and performance-optimized .NET/.NET Core applications.