Merge pull request #308729 from flang-msft/fxl---remove-reddison

Fxl   remove reddison

Author: denrea

articles/redis/best-practices-client-libraries.md

@@ -1,8 +1,9 @@
 ---
 title: Best practices using client libraries with Azure Managed Redis
 description: Learn about client libraries for Azure Managed Redis.
-ms.date: 05/18/2025
-ms.topic: conceptual
+ms.date: 11/24/2025
+ms.topic: article
+
 ms.custom:
   - devx-track-java
   - devx-track-javaee
@@ -17,29 +18,30 @@ appliesto:
 
 # Azure Managed Redis Client libraries
 
-Azure Managed Redis is based on the popular in-memory data store, Redis. Redis clients for many programming languages can access Azure Managed Redis. Each client library has its own API that makes calls to Redis server using Redis commands, but the client libraries are built to talk to any Redis server.
+This article helps you choose and use the best client libraries for Azure Managed Redis. You learn which libraries to use for your programming language, how to handle clustering policies, and avoid common connection issues.
+
+Azure Managed Redis is based on the popular in-memory data store, Redis. Redis clients for many programming languages can access Azure Managed Redis. Each client library has its own API that makes calls to Redis server using Redis commands, but the client libraries are built to talk to any Redis server.
 
 Each client library maintains its own reference documentation. The libraries also provide links to get support through the client library developer community. The Azure Managed Redis team doesn't own the development, or the support for any client libraries.
 
 The following recommendations are based on popularity and whether there's an active online community to support and answer your questions. We only recommend using the latest available version, and upgrading regularly as new versions become available. These libraries are under active development and often release new versions with improvements to reliability and performance.
 
 | **Client library**        | **Language** | **GitHub** **repo**                                                 | **Documentation**                                                                    |
 |---------------------------|--------------|---------------------------------------------------------------------|--------------------------------------------------------------------------------------|
-| StackExchange.Redis       | C#/.NET      | [Link](https://github.com/StackExchange/StackExchange.Redis)        | [More information here](https://stackexchange.github.io/StackExchange.Redis/)        |
-| Lettuce                   | Java         | [Link](https://github.com/lettuce-io/)                              | [More information here](https://lettuce.io/)                                         |
-| Jedis                     | Java         | [Link](https://github.com/redis/jedis)                              |                                                                                      |
-| node_redis                | Node.js      | [Link](https://github.com/redis/node-redis)                         |                                                                                      |
-| Redisson                  | Java         | [Link](https://github.com/redisson/redisson)                        | [More information here](https://redisson.org/)                                       |
-| ioredis                   | Node.js      | [Link](https://github.com/luin/ioredis)                             | [More information here](https://ioredis.readthedocs.io/en/stable/API/)               |
+| StackExchange.Redis       | C#/.NET      | [StackExchange.Redis GitHub](https://github.com/StackExchange/StackExchange.Redis)        | [StackExchange.Redis docs](https://stackexchange.github.io/StackExchange.Redis/)        |
+| Lettuce                   | Java         | [Lettuce GitHub](https://github.com/lettuce-io/)                              | [Lettuce documentation](https://lettuce.io/)                                         |
+| Jedis                     | Java         | [Jedis GitHub](https://github.com/redis/jedis)                              | [Jedis documentation](https://github.com/redis/jedis#readme)                                                                                      |
+| node_redis                | Node.js      | [node_redis GitHub](https://github.com/redis/node-redis)                         | [node_redis documentation](https://github.com/redis/node-redis#readme)                                                                                      |
+| ioredis                   | Node.js      | [ioredis GitHub](https://github.com/luin/ioredis)                             | [ioredis API reference](https://ioredis.readthedocs.io/en/stable/API/)               |
 
 > [!NOTE]
-> Your application can use any client library that is compatible with open-source Redis to connect to your Azure Managed Redis instance.
+> Your application can use any client library that's compatible with open-source Redis to connect to your Azure Managed Redis instance.
 
 ## Choosing the right client library based on your clustering policy
 
 Azure Managed Redis supports the Enterprise clustering policy and the OSS clustering policy. See more information here (add link to clustering policy information).
 
-All client libraries work with your Redis instance with Enterprise clustering policy. However, if you're using the OSS clustering policy, ensure that the client library you choose supports connecting to clustered Redis instances.
+All client libraries work with your Redis instance with Enterprise clustering policy. However, if you're using the OSS clustering policy, ensure that the selected client library supports connecting to clustered Redis instances.
 
 ## Blocked commands
 
@@ -68,64 +70,20 @@ In Active-Active databases, multi-key write commands (`DEL`, `MSET`, `UNLINK`) c
 
 ## Client library-specific guidance
 
-For information on client library-specific guidance best practices, see the following links:
-
-- [StackExchange.Redis (.NET)](best-practices-connection.md#using-forcereconnect-with-stackexchangeredis)
-- [Lettuce (Java)](https://github.com/Azure/AzureCacheForRedis/blob/main/Lettuce%20Best%20Practices.md)
-- [Jedis (Java)](https://github.com/Azure/AzureCacheForRedis/blob/main/Redis-BestPractices-Java-Jedis.md)
-- [Redisson (Java)](best-practices-client-libraries.md#redisson-java)
-- [Node.js](https://github.com/Azure/AzureCacheForRedis/blob/main/Redis-BestPractices-Node-js.md)
-- [PHP](https://github.com/Azure/AzureCacheForRedis/blob/main/Redis-BestPractices-PHP.md)
-- [HiRedisCluster](https://github.com/Azure/AzureCacheForRedis/blob/main/HiRedisCluster%20Best%20Practices.md)
-
-## Redisson (Java)
-
-We _recommend_ you  use redisson 3.14.1 or higher. Older versions contain known connection leak issues that cause problems after failovers. Monitor the Redisson changelog for other known issues can affect features used by your application. For more information, see[`CHANGELOG`](https://github.com/redisson/redisson/blob/master/CHANGELOG.md) and the [Redisson FAQ](https://github.com/redisson/redisson/wiki/16.-FAQ).
-
-Other notes:
-
-- Redisson defaults to 'read from replica' strategy, unlike some other clients. To change this default, modify the 'readMode' config setting.
-- Redisson has a connection pooling strategy with configurable minimum and maximum settings, and the default minimum values are large. The large defaults could contribute to aggressive reconnect behaviors or 'connection storms.' To reduce the risk, consider using fewer connections because you can efficiently pipeline commands, or batches of commands, over a few connections.
-- Redisson has a default idle connection time-out of 10 seconds, which leads to more closing and reopening of connections than ideal.
-
-Here's a recommended baseline configuration for cluster mode that you can modify as needed:
-
-```yml
-clusterServersConfig:
-  idleConnectionTimeout: 30000
-  connectTimeout: 15000
-  timeout: 5000
-  retryAttempts: 3
-  retryInterval: 3000
-  checkLockSyncedSlaves: false
-  failedSlaveReconnectionInterval: 15000
-  failedSlaveCheckInterval: 60000
-  subscriptionsPerConnection: 5
-  clientName: "redisson"
-  loadBalancer: !<org.redisson.connection.balancer.RoundRobinLoadBalancer> {}
-  subscriptionConnectionMinimumIdleSize: 1
-  subscriptionConnectionPoolSize: 50
-  slaveConnectionMinimumIdleSize: 2
-  slaveConnectionPoolSize: 24
-  masterConnectionMinimumIdleSize: 2
-  masterConnectionPoolSize: 24
-  readMode: "MASTER"
-  subscriptionMode: "MASTER"
-  nodeAddresses:
-  - "redis://mycacheaddress:10000"
-  scanInterval: 1000
-  pingConnectionInterval: 60000
-  keepAlive: false
-  tcpNoDelay: true
-```
-
-For an article about Redisson's support for JCache as the store for HTTP session state in IBM Liberty on Azure, see [Use Java EE JCache with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache).
+Choose your programming language to get detailed best practices and connection guidance:
+
+- [StackExchange.Redis (.NET) best practices](best-practices-connection.md#using-forcereconnect-with-stackexchangeredis)
+- [Lettuce (Java) best practices](https://github.com/Azure/AzureCacheForRedis/blob/main/Lettuce%20Best%20Practices.md)
+- [Jedis (Java) best practices](https://github.com/Azure/AzureCacheForRedis/blob/main/Redis-BestPractices-Java-Jedis.md)
+- [Node.js best practices](https://github.com/Azure/AzureCacheForRedis/blob/main/Redis-BestPractices-Node-js.md)
+- [PHP best practices](https://github.com/Azure/AzureCacheForRedis/blob/main/Redis-BestPractices-PHP.md)
+- [HiRedisCluster best practices](https://github.com/Azure/AzureCacheForRedis/blob/main/HiRedisCluster%20Best%20Practices.md)
 
 ## How to use client libraries
 
 Besides the reference documentation, you can find tutorials showing how to get started with Azure Managed Redis using different languages and cache clients.
 
-For more information on using some of these client libraries in tutorials, see the following articles:
+For more information on using some of these client libraries in tutorials, see the following articles:
 
 - [Code a .NET Framework app](dotnet-how-to-use-azure-redis-cache.md)
 - [Code a .NET Core app](dotnet-core-quickstart.md)

articles/redis/includes/managed-redis-create.md

@@ -1,16 +1,18 @@
 ---
-ms.date: 05/18/2025
+ms.date: 11/24/2025
 ms.topic: include
 ms.custom:
   - ignite-2024
   - build-2025
 ---
 
-1. To create an Azure Managed Redis instance, sign in to the Azure portal and select **Create a resource**.
+1. To create an Azure Managed Redis instance, sign in to the Azure portal and select **Create a resource**. 
 
-1. On the **New** page, in the search box type **Azure Cache for Redis**.
-  
-1. On the **New Redis Cache** tab, configure the settings for your new cache on the Basics .
+1. On the **Create a resource** page, type **Azure Managed Redis** in the search box.
+
+1. Select the **Azure Managed Redis** tile and select **Create**.
+
+1. On the **Create Azure Managed Redis instance** pane, configure the settings for a new cache on the **Basics** tab.
 
    | Setting      |  Choose a value  | Description |
    | ------------ |  ------- | -------------------------------------------------- |
@@ -20,47 +22,44 @@ ms.custom:
    | **Region** | Drop down and select a location. | Azure Managed Redis is available in selected Azure regions. |
    | **Data tier** | Select either **In-memory** for high-performance, or **Flash** for lower performance caches  | The in-memory tiers include **Balanced**, **Memory Optimized**, and **Compute Optimized**. Use the **Flash** tier to use in-memory (RAM) and on-disk (SSD) data storage. |
    | **Cache Size** | Drop down and select a size. | Cache size depends on tier. The smallest size is a Balanced tier. The size largest in-memory tier is a Memory Optimized tier. |
-   | **Performance** | Drop down and select a performance preference. | Performance depends on the number of vCPUs. Number of vCPU varies with tier. Compute Optimized has the most vCPUs. | 
+   | **Performance** | Drop down and select a performance preference. | Performance depends on the number of vCPUs. Number of vCPU varies with tier. Compute Optimized has the most vCPUs. |
 
     For guidance on choosing the right performance tier, see [Choosing the right tier](../overview.md#choosing-the-right-tier).
-   <!-- :::image type="content" source="media/managed-redis-create/managed-redis-new-cache-basics.png" alt-text="Screenshot showing the Azure Managed Redis Basics tab."::: -->
 
    [!INCLUDE [tier-preview](tier-preview.md)]
 
-1. Select **Next: Networking** , and select either a **Public Endpoint** or **Private Endpoint**.
+1. Select **Next: Networking** , and select either a **Disable public access and use private access** or **Enable public access from all networks**.
 
 1. Select **Next: Active geo-replication**. To use active geo-replication it must be enabled during provisioning. Caches without active geo-replication can't be added to or join active geo-replication groups later. For more information, see [Configure active geo-replication for Azure Managed Redis instances](../how-to-active-geo-replication.md).
 
 1. Select the **Next: Advanced** tab.
 
    Configure any [Redis modules](../redis-modules.md) you want to add to the instance.
 
-   By default, for a new managed cache:
-     - Microsoft Entra ID is enabled.
-     - **Access Keys Authentication** is disabled for security reasons.
-
-   > [!IMPORTANT]
-   > For optimal security, we recommend that you use Microsoft Entra ID with managed identities to authorize requests against your cache if possible. Authorization by using Microsoft Entra ID and managed identities provides superior security and ease of use over shared access key authorization. For more information about using managed identities with your cache, see [Use Microsoft Entra ID for cache authentication](/azure/azure-cache-for-redis/cache-azure-active-directory-for-authentication).
-
    Set **Clustering policy**:
     - Use **Enterprise** in order to use RedisSearch or other modules
     - Use **OSS** for a clustered cache.
     - Use **Non-clustered (Preview)** for a non-clustered cache.
 
    For more information on choosing **Clustering policy**, see [Cluster policy](../architecture.md#cluster-policies).
 
-   <!-- :::image type="content" source="media/managed-redis-create/managed-redis-advanced-settings.png" alt-text="Screenshot that shows the Azure Managed Redis Advanced tab."::: -->
+   By default, for a new managed cache:
+     - Microsoft Entra ID is enabled.
+     - **Access Keys Authentication** is disabled for security reasons.
 
    > [!IMPORTANT]
-   > You can't change the clustering policy of an Azure Managed Redis instance after you create it. If you're using [RediSearch](../redis-modules.md#redisearch), the Enterprise cluster policy is required, and `NoEviction` is the only eviction policy supported.
+   > You can't change modules after you create a cache instance. Modules must be enabled at the time you create an Azure Managed Redis instance. There is no option to enable the configuration of a module after you create a cache.
    >
 
    > [!IMPORTANT]
-   > If you're using this cache instance in a geo-replication group, eviction policies cannot be changed after the instance is created. Be sure to know the eviction policies of your primary nodes before you create the cache. For more information on active geo-replication, see [Active geo-replication prerequisites](../how-to-active-geo-replication.md#active-geo-replication-prerequisites).
+   > For optimal security, we recommend that you use Microsoft Entra ID with managed identities to authorize requests against your cache if possible. Authorization by using Microsoft Entra ID and managed identities provides superior security and ease of use over shared access key authorization. For more information about using managed identities with your cache, see [Use Microsoft Entra ID for cache authentication](/azure/azure-cache-for-redis/cache-azure-active-directory-for-authentication).
+
+   > [!IMPORTANT]
+   > You can't change the clustering policy of an Azure Managed Redis instance after you create it. If you're using [RediSearch](../redis-modules.md#redisearch), the Enterprise cluster policy is required, and `NoEviction` is the only eviction policy supported.
    >
 
    > [!IMPORTANT]
-   > You can't change modules after you create a cache instance. Modules must be enabled at the time you create an Azure Cache for Redis instance. There is no option to enable the configuration of a module after you create a cache.
+   > If you're using this cache instance in a geo-replication group, eviction policies cannot be changed after the instance is created. Be sure to know the eviction policies of your primary nodes before you create the cache. For more information on active geo-replication, see [Active geo-replication prerequisites](../how-to-active-geo-replication.md#active-geo-replication-prerequisites).
    >
 
 1. Select **Next: Tags** and skip.

articles/redis/includes/media/managed-redis-create/managed-redis-advanced-settings.png

@@ -1,5 +1,5 @@
 ---
-ms.date: 05/18/2025
+ms.date: 11/24/2025
 ms.topic: include
 ms.custom:
   - build-2025
@@ -18,7 +18,7 @@ Otherwise, if you're finished with the quickstart sample application, you can de
 
 1. In the **Filter by name** textbox, type the name of your resource group. The instructions for this article used a resource group named `TestResources`. On your resource group in the result list, select **Test Resources** then **Delete resource group**.
 
-   :::image type="content" source="../media/java-redisson-get-started/redis-cache-delete-resource-group.png" alt-text="Screenshot of the Azure portal that shows the Resource group page with the Delete resource group button highlighted." lightbox="../media/java-redisson-get-started/redis-cache-delete-resource-group.png":::
+   :::image type="content" source="media/cache-delete-resource-group/cache-confirm-deletion.png" alt-text="Screenshot of the Azure portal that shows the Resource group page with the Delete resource group button highlighted."  lightbox="media/cache-delete-resource-group/cache-delete-resource-group.png":::
 
 1. Type the name of your resource group to confirm deletion and then select **Delete**.