Skip to content

Commit 61aa2c6

Browse files
committed
touchups
1 parent d9fd683 commit 61aa2c6

File tree

3 files changed

+21
-15
lines changed

3 files changed

+21
-15
lines changed

articles/azure-cache-for-redis/cache-best-practices-client-libraries.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about recommended client libraries for Azure Cache for Redis,
44

55

66
ms.topic: conceptual
7-
ms.date: 04/30/2025
7+
ms.date: 05/05/2025
88
appliesto:
99
- ✅ Azure Cache for Redis
1010
ms.custom: devx-track-java, devx-track-javaee, devx-track-javaee-liberty, devx-track-javaee-liberty-aks, devx-track-extended-java, ignite-2024
@@ -16,7 +16,7 @@ Azure Cache for Redis is based on the Redis open-source, in-memory data store. R
1616

1717
Each client library has its own API that calls Redis servers using Redis commands. The client libraries are built to communicate with any Redis server.
1818

19-
Each client maintains reference documentation for its own library, and provides links to get support through the client library developer community. Microsoft and the Azure Redis team don't own the development or support for any client libraries.
19+
Clients maintain reference documentation for their own libraries, and provides links to get support through the client library developer community. Microsoft and the Azure Redis team don't own the development or support for any client libraries.
2020

2121
Microsoft and Azure Redis do recommend some libraries, based on popularity and whether there's an active online support community to answer questions. These libraries are under active development and often release new versions with reliability and performance improvements. Microsoft recommends using the latest available version, and upgrading regularly as new versions become available.
2222

@@ -60,7 +60,7 @@ Besides the reference documentation, you can use the following tutorials to get
6060

6161
## Best practices for Redisson (Java)
6262

63-
Here are some recommended best practices for the Redisson client library:
63+
Here are some recommended best practices for the [Redisson](https://redisson.pro/) client library:
6464

6565
- Use Redisson 3.14.1 or higher. Older versions contain known connection leak issues that cause problems after failovers.
6666

@@ -74,7 +74,7 @@ Here are some recommended best practices for the Redisson client library:
7474

7575
- Reset the idle connection timeout if necessary. Redisson has a default 10-second idle connection timeout, which can lead to more closing and reopening of connections than ideal.
7676

77-
- For an article about Redisson support for Java EE JCache as the store for HTTP session state in IBM Liberty on an Azure Kubernetes Service (AKS) cluster, see [Using Azure Redis as session cache for WebSphere Liberty or Open Liberty](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache).
77+
- See [Using Azure Redis as session cache for WebSphere Liberty or Open Liberty](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache) for information about using Redisson with Java EE JCache to store HTTP session state on an Azure Kubernetes Service (AKS) cluster in IBM Libery.
7878

7979
- Use the following recommended baseline configuration for cluster mode, and modify it as needed.
8080

articles/azure-cache-for-redis/cache-planning-faq.yml

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ metadata:
66

77

88
ms.topic: faq
9-
ms.date: 04/30/2025
9+
ms.date: 05/05/2025
1010
appliesto:
1111
- ✅ Azure Cache for Redis
1212
title: Azure Cache for Redis planning FAQs
@@ -37,20 +37,15 @@ sections:
3737
| US Government | *.redis.cache.usgovcloudapi.net |
3838
| 21Vianet Cloud (China) | *.redis.cache.chinacloudapi.cn |
3939
40-
For other considerations about using Azure Redis with other clouds, see the following links:
40+
The Azure Redis Enterprise and Enterprise Flash tiers are available only in the Public cloud.
41+
42+
For more considerations about using Azure Redis with other clouds, see the following links:
4143
4244
- [Azure Government Databases](/azure/azure-government/compare-azure-government-global-azure)
4345
- [Azure operated by 21Vianet Cloud](https://www.azure.cn/home/features/redis-cache/)
4446
4547
For information about using Azure Redis with PowerShell in Azure Government Cloud and Azure operated by 21Vianet Cloud, see [How to connect to other clouds - PowerShell](../redis/how-to-manage-redis-cache-powershell.md#how-to-connect-to-other-clouds).
4648
47-
The Azure Redis Enterprise and Enterprise Flash tiers are available only in the Public cloud.
48-
49-
- question: |
50-
What region should I locate my cache in?
51-
answer: |
52-
For best performance and lowest latency, locate your Azure Redis cache in the same Azure region as your cache client application.
53-
5449
- question: |
5550
Where does my cached data reside?
5651
answer: |
@@ -65,6 +60,11 @@ sections:
6560
6661
You need to explicitly configure Azure Redis to use the preceding features. You also have complete control over the region where the storage account or secondary cache is located.
6762
63+
- question: |
64+
Which region should I locate my cache in?
65+
answer: |
66+
For best performance and lowest latency, locate your Azure Redis cache in the same Azure region as your cache client application.
67+
6868
additionalContent: |
6969
7070
## Related content

articles/azure-cache-for-redis/cache-tls-configuration.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,17 @@ description: Learn about the TLS protocol configuration and how to use TLS to se
77
ms.topic: overview
88
ms.custom:
99
- ignite-2024
10-
ms.date: 01/23/2024
10+
ms.date: 05/05/2025
1111
appliesto:
1212
- ✅ Azure Cache for Redis
1313
# Customer intent: As a developer creating a service that uses a cache, I want to know the details about TLS connections so that I know my service is secure.
1414
---
1515

1616
# Azure Cache for Redis TLS protocol configuration settings
1717

18-
Transport Layer Security (TLS) is a cryptographic protocol that provides secure communication over a network. Azure Cache for Redis supports TLS on all tiers. When you create a service that uses an Azure Redis cache, it's best to connect using TLS.
18+
Transport Layer Security (TLS) is a cryptographic protocol that provides secure communication over a network. Azure Cache for Redis supports TLS on all tiers, and requires TLS encrypted communications by default. Using TLS is recommended as a best practice across virtually all Azure Redis use cases.
19+
20+
The option to connect Azure Redis without TLS is included for backwards compatibility purposes. If your client library or tool doesn't support TLS, you can enable unencrypted connections through the [Azure portal](cache-configure.md#access-ports) or [management APIs](/rest/api/redis/redis/update). This article describes how to enable non-TLS access by using the Azure portal.
1921

2022
> [!IMPORTANT]
2123
> TLS 1.0 and 1.1 are no longer supported. For more information, see [Remove TLS 1.0 and 1.1 from use with Azure Cache for Redis](cache-remove-tls-10-11.md),
@@ -42,6 +44,10 @@ The TLS 1.3 cipher suites are as follows:
4244
4345
## How to enable or disable TLS
4446

47+
Azure Cache for Redis
48+
49+
50+
4551
Enabling and disabling TLS is different for different Azure Redis tiers.
4652

4753
### Basic, Standard, and Premium tiers

0 commit comments

Comments
 (0)