| title | description | author | ms.author | ms.service | ms.topic | ms.date |
|---|---|---|---|---|---|---|
What's New in Azure Cache for Redis |
Recent updates for Azure Cache for Redis |
flang-msft |
franlanglois |
cache |
conceptual |
02/06/2023 |
Support for using the RedisJSON module has now reached General Availability (GA).
For more information, see Use Redis modules with Azure Cache for Redis.
All versions of Azure Cache for Redis REST API, PowerShell, Azure CLI and Azure SDK, will create Redis instances using Redis 6 starting January 20, 2023. Previously, we announced this change would take place on November 1, 2022, but due to unforeseen changes, the date has now been pushed out to January 20, 2023.
For more information, see Redis 6 becomes default for new cache instances.
Several enhancements have been made to the passive geo-replication functionality offered on the Premium tier of Azure Cache for Redis.
-
New metrics are available for customers to better track the health and status of their geo-replication link, including statistics around the amount of data that is waiting to be replicated. For more information, see Monitor Azure Cache for Redis.
- Geo Replication Connectivity Lag (preview)
- Geo Replication Data Sync Offset (preview)
- Geo Replication Full Sync Event Finished (preview)
- Geo Replication Full Sync Event Started (preview)
-
Customers can now initiate a failover between geo-primary and geo-replica caches with a single selection or CLI command, eliminating the hassle of manually unlinking and relinking caches. For more information, see Initiate a failover from geo-primary to geo-secondary.
-
A global cache URL is also now offered that automatically updates their DNS records after geo-failovers are triggered, allowing their application to manage only one cache address. For more information, see Geo-primary URL.
On June 30, 2023, we'll retire version 4 for Azure Cache for Redis instances. Before that date, you need to upgrade any of your cache instances to version 6.
- All cache instances running Redis version 4 after June 30, 2023 will be upgraded automatically.
- All cache instances running Redis version 4 that have geo-replication enabled will be upgraded automatically after August 30, 2023.
We recommend that you upgrade your caches on your own to accommodate your schedule and the needs of your users to make the upgrade as convenient as possible.
For more information, see Retirements.
Authenticating storage account connections using managed identity has now reached General Availability (GA).
For more information, see Managed identity for storage.
The Enterprise and Enterprise Flash tiers of Azure Cache for Redis now support the RedisJSON module. This module adds native functionality to store, query, and search JSON-formatted data that allows you to store data more easily in a document-style format in Redis. By using this module, you simplify common use cases like storing product catalog or user profile data.
The RedisJSON module implements the community version of the module so you can use your existing knowledge and workstreams. RedisJSON is designed for use with the search functionality of RediSearch. Using both modules provides integrated indexing and querying of data. For more information, see RedisJSON.
The RediSearch module is also now available for Azure Cache for Redis. For more information on using Redis modules in Azure Cache for Redis, see Use Redis modules with Azure Cache for Redis.
Important
Previously, we announced this change would take place on November 1, 2022. The new date is January 20th, 2023. The text has been updated to reflect the new date.
Beginning January 20, 2023, all versions of Azure Cache for Redis REST API, PowerShell, Azure CLI, and Azure SDK will create Redis instances using the latest stable version of Redis offered by Azure Cache for Redis by default. Previously, Redis version 4.0 was the default version used. However, as of October 2021, the latest stable Redis version offered in Azure Cache for Redis is 6.0.
Note
This change does not affect any existing instances. It is only applicable to new instances created from January 20, 2023, and onward.
The default Redis version that is used when creating a cache instance can vary because it is based on the latest stable version offered in Azure Cache for Redis.
If you need a specific version of Redis for your application, we recommend using latest artifact versions as shown in the table below. Then, choose the Redis version explicitly when you create the cache.
| Artifact | Version that supports specifying Redis version |
|---|---|
| REST API | 2020-06-01 and newer |
| PowerShell | 6.3.0 and newer |
| Azure CLI | 2.27.0 and newer |
| Azure SDK for .NET | 7.0.0 and newer |
| Azure SDK for Python | 13.0.0 and newer |
| Azure SDK for Java | 2.2.0 and newer |
| Azure SDK for JavaScript | 6.0.0 and newer |
| Azure SDK for Go | v49.1.0 and newer |
These two new metrics can help identify whether Azure Cache for Redis clients are frequently disconnecting and reconnecting, which can cause higher CPU usage and Redis Server Load.
- Connections Created Per Second
- Connections Closed Per Second
For more information, see View cache metrics.
On May 15, 2022, all new Azure Cache for Redis instances will use Redis 6 by default. You can still create a Redis 4 instance by explicitly selecting the version when you create an Azure Cache for Redis instance.
This change doesn't affect any existing instances. The change is only applicable to new instances created after May 15, 2022.
The default version of Redis that is used when creating a cache can change over time. Azure Cache for Redis might adopt a new version when a new version of open-source Redis is released. If you need a specific version of Redis for your application, we recommend choosing the Redis version explicitly when you create the cache.
As of May 2022, Azure Cache for Redis rolls over to TLS certificates issued by DigiCert Global G2 CA Root. The current Baltimore CyberTrust Root expires in May 2025, requiring this change.
We expect that most Azure Cache for Redis customers won't be affected. However, your application might be affected if you explicitly specify a list of acceptable certificate authorities (CAs), known as certificate pinning.
For more information, read this blog that contains instructions on how to check whether your client application is affected. We recommend taking the actions recommended in the blog to avoid cache connectivity loss.
Active geo-replication for Azure Cache for Redis Enterprise is now generally available (GA).
Active geo-replication is a powerful tool that enables Azure Cache for Redis clusters to be linked together for seamless active-active replication of data. Your applications can write to one Redis cluster and your data is automatically copied to the other linked clusters, and vice versa. For more information, see this post in the Azure Developer Community Blog.
Azure Cache for Redis now supports authenticating storage account connections using managed identity. Identity is established through Azure Active Directory, and both system-assigned and user-assigned identities are supported. Support for managed identity further allows the service to establish trusted access to storage for uses including data persistence and importing/exporting cache data.
For more information, see Managed identity with Azure Cache for Redis.
Azure Cache for Redis 6.0 is now generally available. The new version includes:
- Redis Streams, a new data type
- Performance enhancements
- Enhanced developer productivity
- Boosts security
You can now use an append-only data structure, Redis Streams, to ingest, manage, and make sense of data that is continuously being generated.
Additionally, Azure Cache for Redis 6.0 introduces new commands: STRALGO, ZPOPMIN, ZPOPMAX, and HELP for performance and ease of use.
Get started with Azure Cache for Redis 6.0, today, and select Redis 6.0 during cache creation. Also, you can upgrade your existing Redis 4.0 cache instances. For more information, see Set Redis version for Azure Cache for Redis.
Azure Cache for Redis now integrates with Azure diagnostic settings to log information on all client connections to your cache. Logging and then analyzing this diagnostic setting helps you understand who is connecting to your caches and the timestamp of those connections. This data could be used to identify the scope of a security breach and for security auditing purposes. Users can route these logs to a destination of their choice, such as a storage account or Event Hubs.
For more information, see Monitor Azure Cache for Redis data using diagnostic settings.
Active geo-replication public preview now supports:
- RediSearch Module: Deploy RediSearch with active geo-replication
- Five caches in a replication group. Previously, supported two caches.
- OSS clustering policy - suitable for high-performance workloads and provides better scalability.
Microsoft is updating Azure services to use TLS certificates from a different set of Root Certificate Authorities (CAs). This change is being made because the current CA certificates don't comply with one of the CA/Browser Forum Baseline requirements. For full details, see Azure TLS Certificate Changes.
For more information on the effect to Azure Cache for Redis, see Azure TLS Certificate Change.
If you have more questions, contact us through support.