What's New in NCache 5.3.8?
Oct 21, 2026
NCache 5.3.8 (October 2026) is a long-term support (LTS) release that adds fully managed NCache Cloud on Azure and AWS, a Redis RESP Protocol Server, a thin client, live upgrades, OpenTelemetry and Helm charts. This page covers 5.3.8 plus highlights from 5.3 SP7 (July 2026) and 5.3 SP5 (May 2025).
Upgrading from an earlier release? See the full NCache release notes for every change.
NCache Cloud: Fully Managed on Azure and AWS Marketplace
Added in 5.3.8
NCache Cloud runs a fully managed NCache cluster on Azure or AWS. Buy it through Azure or AWS Marketplace on Hourly (pay-as-you-go) or BYOL plans, with a free trial.
The NCache Cloud Portal, built into the NCache Management Center, lets you:
- 1-click deployment, including multi-region
- 1-click scaling
- Marketplace Plans: Hourly, Free Trial, BYOL
- Automatic OS patching and product upgrades
- Runs 100% inside your Cloud subscription
- NCache Cloud Portal with Microsoft Entra ID (Azure) or Amazon Cognito (AWS) security
- Azure Monitor and Amazon CloudWatch integration
NCache Cloud
Redis RESP Protocol Server for Windows
Added in 5.3.8
NCache has developed a Redis RESP Protocol Server.
- Built natively in .NET on Windows
- Redis RESP Protocol compatibility
- Use existing Redis client libraries
- Windows-native administration and monitoring
- Enterprise Windows security
NCache RESP Server
Live (Rolling) Upgrades for MINOR and PATCH Releases
Added in 5.3.8
- NCache now follows semantic versioning (MAJOR.MINOR.PATCH).
- MINOR and PATCH releases upgrade one cluster node at a time while the cache stays up.
- Older clients keep working.
- MAJOR upgrades use a separate process, and client applications must be recompiled against the new client SDK.
NCache Live Upgrade
Full-Data Client Cache
Added in 5.3 SP5
Cache complete datasets of selected classes on the client, kept in sync with the cache cluster. Two options control behavior:
- Caches Complete Datasets Locally: Caches all entries of selected .NET classes, making the complete datasets instantly available.
- Synchronization with Clustered Cache: It remains fully synchronized with the clustered cache to ensure consistency.
- Strict Query Enforcement: Queries fail if the client holds only part of the data.
- Strict Local Reads: a local miss is not fetched from the cluster.
Full Data Client Cache
gMSA Authentication
Added in 5.3 SP7
- Client applications authenticate with Group Managed Service Accounts (gMSA).
- No usernames or passwords sit in client configuration.
- The client obtains a Kerberos token, and the cache server validates it against LDAP.
- Admins add gMSA users or groups in the NCache Management Center or with Add-NCacheUserOrGroup.
gMSA Docs
LDAP Admin Roles
Added in 5.3 SP7
NCache security now separates two roles:
- Machine administrator: the local OS administrator. Only this role can enable or disable security.
- Node-admins: LDAP/Active Directory users or groups that manage access to the node and its caches.
Enabling security requires at least one LDAP-backed node-admin, and the last node-admin cannot be removed.
LDAP Docs
NCache-Provided TLS Certificates with Auto Renewals
Added in 5.3.8
- NCache includes its own certificate authority, so you don't need to obtain or manage TLS certificates yourself.
- NCache issues certificates for cache servers and, with New-NCacheTlsCertificate, for client applications, including on machines without NCache installed.
- Certificates renew automatically.
- Issuance and renewal are authenticated with the email tied to your license.
- Certificates load from PEM or PFX files, and private keys never leave the node.
Note: You can still use your own custom certificates for both TLS and mutual TLS if you prefer.
NCache TLS Docs
Mutual TLS, Including Between Cluster Nodes
Added in 5.3 SP5, extended in 5.3.8
- Mutual TLS uses separate certificates for clients and servers.
- NCache servers generate a certificate for each client application.
- Only applications with an allowed certificate can connect, so the certificate handles both authentication and admission.
- In 5.3.8, mutual TLS also covers traffic between cache cluster nodes.
TLS 1.3
Added in 5.3 SP5
- NCache supports TLS 1.3 for client and server connections.
- This includes clients on .NET Framework 4.6.2 and later.
Encryption Key Management (KEK/CEK/DEK)
Added in 5.3 SP5
NCache protects cached data and stored credentials with three keys, each with its own job:
- Key Encryption Key (KEK): an AES-256 master key set on each cache server. It must be the same on every server in the cluster.
- Data Encryption Key (DEK): encrypts your cached data. The DEK is itself encrypted by the KEK.
- Credentials Encryption Key (CEK): encrypts the credentials client applications store in their configuration (client.ncconf). Usernames and passwords in client config files are never left in plain text, so anyone who can read a config file can't recover them.
The KEK and CEK are master keys: they encrypt other keys and data, and are not encrypted themselves. You can set your own KEK and CEK to customize encryption for stronger security in your environment.
Encryption is turned on and off with the Enable-NCEncryption and Disable-NCEncryption PowerShell cmdlets.
Data Encryption Docs
Thin Client: All Cache and Client Cache Settings Managed on the Server
Added in 5.3.8
Client applications now hold only what they need to connect to the cache:
- Cache name
- Server endpoints and port
- Security credentials, if any
Everything else about client-side configuration is managed on the NCache servers, including Client Cache settings. The servers send these settings to each client at runtime. Clients pick up changes as they happen, with no edits to client config files and no application restarts.
What this means for you:
- One place to manage configuration. Change client behavior across all applications from the server, instead of updating config on every client machine.
- No configuration drift. Every client gets the same settings from the server.
- Simpler deployments. Client config files stay small and rarely change.
- Flexible Client Cache placement. Based on server settings, Client Cache runs InProc inside the application or OutProc, including on a separate machine.
Helm Charts for Kubernetes
Added in 5.3.8
- Deploy NCache on Kubernetes with Helm charts, on-premises or on AKS and EKS.
- One unified chart deploys the cache cluster, Gateway Services and Discovery Service.
- Separate configurations for Development/QA and Production.
- NCache talks to the Kubernetes API server directly.
Kubernetes Docs
Docker Compose Deployment
Added in 5.3.8
- Run NCache with Docker Compose, published as an OCI artifact on Docker Hub.
- Each deployment includes an Nginx load balancer, so clients and management tools use a single endpoint.
- TLS is configured through environment variables.
Docker Compose Docs
OpenTelemetry
Added in 5.3.8
- Publish NCache performance counters and logs to any OpenTelemetry collector, configured per cache.
- The NCache Management Center generates the collector YAML.
- Set-NCacheOpenTelemetry sets endpoints and protocols.
- Clients receive the metrics endpoint from the server when they connect.
- Client metrics are load-balanced across server-side collectors.
Built-in Prometheus Metrics, plus JSON Metrics
Added in 5.3.8
- Prometheus metrics are served directly by NCache and are on by default.
- No separate Metric Server to run.
- A new /metrics/json endpoint returns the same counters as JSON.
- Client counters are exposed on the same endpoints through the NCache Service.
Health Check Endpoints
Added in 5.3.8
The NCache Service detects processes that are running but unresponsive. It exposes three endpoints on port 9804:
- /livez: the service is responsive
- /readyz: the service is ready for cache traffic
- /health: detailed health for each cache host
Azure VMSS and AWS Auto Scaling groups use these endpoints to judge node health.
NCache Client: OutProc Client Cache and Monitoring
Added in 5.3.8
NCache Client hosts the OutProc Client Cache and collects client-side performance counters for your applications. It works the same way whether your applications run on Windows servers, in Docker or in Kubernetes.
On Windows
- As before, the NCache Service runs on the application machine. When the server settings call for OutProc Client Cache, the service creates and hosts it.
- An OutProc Client Cache can also run on a separate machine from the application.
- The NCache Service also collects client counters, including from applications using InProc Client Cache, and exposes them on the built-in Prometheus and JSON metrics endpoints.
On Docker and Kubernetes
- NCache Client runs as its own container (Docker) or service (Kubernetes) alongside your application containers.
- It hosts the OutProc Client Cache and publishes client counters, just like the NCache Service on Windows.
- Applications find it through the NCACHE_CLIENT_HOST environment variable:
- Bridge networking: set it to the NCache Client container or service name.
- Host networking: set it to localhost.
- The NCache Docker Compose deployment includes the NCache Client container.
Monitoring
- Client Cache statistics appear on the Monitor page in the NCache Management Center.
- Client error logging is on by default.
Post Event Actions
Added in 5.3 SP7
- Run your own scripts automatically after server operations succeed.
- Triggers include starting or stopping services, caches and nodes, creating or removing caches, and adding or removing client nodes.
- Actions are defined in post-action.ncconf and can be turned on or off individually.
- Each script receives a JSON payload with the operation details.
Graceful Shutdown Handling
Added in 5.3 SP7
- When a server shuts down or restarts, NCache stops its caches.
- It tells the rest of the cluster right away, instead of waiting for a timeout.
- In Docker and Kubernetes, NCache receives the shutdown signal directly.
- It finishes flushing write-behind queues before the container stops.
.NET 10 Support: NCache Server Built on .NET 10
Added in 5.3 SP7
The NCache server is built on .NET 10, Microsoft's latest long-term support release. One modern server runtime runs NCache wherever you deploy it:
- Windows Server: runs as a Windows service.
- Linux: runs as a systemd service.
- Windows Containers: available as a lightweight Nano Server image.
- Docker Containers: for development, test and production on any Docker host.
- Kubernetes: deploys with Helm charts on-premises or on AKS and EKS.
Because the same .NET 10 server runs on every platform, NCache behaves the same way everywhere. You can move between on-premises, containers and the cloud without changing your application.
On Windows Server and Linux, install the .NET 10 runtime before installing NCache.
Client Support for .NET 8, 9 and 10
Added in 5.3.8
- The NCache client NuGet package targets .NET 8 and later.
- Applications on .NET 8, 9 and 10 use the same client.
Client Support for .NET Framework 4.0 to 4.8
Added in 5.3.8
- Applications on .NET Framework 4.0 through 4.8 can use the NCache 5.3.8 client.
- Older applications can use the latest NCache servers without being migrated to modern .NET first.
- Earlier 5.3 releases temporarily dropped support for older .NET Framework versions and required .NET Framework 4.6.2 or later.
- 3.8 restores full support for every version from 4.0 through 4.8.
Windows Server 2025 Support
Added in 5.3 SP5
- Supports Windows Server 2025.
- Supports Windows Server 2022.
New Integrations
Added in 5.3.8
- HybridCache
- FusionCache, with IDistributedCache
- Dapper
- Distributed Locking
- ITicketStore
EF Core 10 Support
Added in 5.3.8
- The NCache Entity Framework Core provider supports EF Core 10.
Before You Upgrade to 5.3.8
5.3.8 includes changes that affect existing deployments. Review these before upgrading, and see the release notes for details.
- New ports: NCache now uses ports 9800–9900. Update firewall and load balancer rules before upgrading.
- Mirror Cache removed: the Mirror Cache topology is discontinued.
- JMX and SNMP removed: move monitoring to OpenTelemetry or the built-in Prometheus endpoints.
- Metric Server retired: Prometheus metrics are now served by NCache itself.
- Licensing cmdlets renamed: Register-NCacheEvaluation is now Register-NCache, and the old Register-NCache is now Register-NCacheLicense. Update your scripts.
- Client connection settings moved to the server: connection properties on CacheConnectionOptions no longer take effect.
- New default cache name: DemoCache is now DefaultCache.
- New prerequisites: install PowerShell Core and the .NET 10 runtime before installing NCache.