You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Cache for Redis is based on the popular open-source in-memory data store, open-source 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.
15
+
Azure Cache for Redis is based on the Redis open-source, in-memory data store. Redis clients for many programming languages can access Azure Redis. Your application can use any client library that's compatible with open-source Redis to connect to your Azure Redis cache.
16
16
17
-
Each client maintains its own reference documentation for its library. The clients also provide links to get support through the client library developer community. The Azure Cache for Redis team doesn't own the development, or the support for any client libraries.
17
+
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.
18
18
19
-
Although we don't own or support any client libraries, we do recommend some libraries. 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.
19
+
Clients maintain reference documentation for their own libraries, and provide 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.
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.
22
+
23
+
The following table lists links and documentation for some recommended client libraries.
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).
48
-
49
-
Other notes:
50
-
51
-
- Redisson defaults to 'read from replica' strategy, unlike some other clients. To change this default, modify the 'readMode' config setting.
52
-
- 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.
53
-
- Redisson has a default idle connection time out of 10 seconds, which leads to more closing and reopening of connections than ideal.
54
-
55
-
Here's a recommended baseline configuration for cluster mode that you can modify as needed:
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).
Besides the reference documentation, you can find tutorials showing how to get started with Azure Cache for Redis using different languages and cache clients.
91
-
92
-
For more information on using some of these client libraries in tutorials, see the following articles:
51
+
Besides the reference documentation, you can use the following tutorials to get started with Azure Redis using different languages and cache clients:
93
52
94
53
-[Code a .NET Framework app](../redis/dotnet-how-to-use-azure-redis-cache.md)
95
54
-[Code a .NET Core app](../redis/dotnet-core-quickstart.md)
@@ -99,7 +58,56 @@ For more information on using some of these client libraries in tutorials, see
99
58
-[Code a Node.js app](../redis/nodejs-get-started.md)
100
59
-[Code a Python app](../redis/python-get-started.md)
101
60
102
-
## Next steps
61
+
## Best practices for Redisson (Java)
62
+
63
+
Here are some recommended best practices for the [Redisson](https://redisson.pro/) client library:
64
+
65
+
- Use Redisson 3.14.1 or higher. Older versions contain known connection leak issues that cause problems after failovers.
66
+
67
+
- Monitor the Redisson changelog for known issues that can affect features your application uses. For more information, see the [Redisson Releases History](https://github.com/redisson/redisson/blob/master/CHANGELOG.md) and the [Redisson FAQ](https://redisson.pro/docs/faq/).
68
+
69
+
- Modify the `readMode` config setting if you don't want to use the *read from replica* strategy. Unlike some other clients, Redisson uses *read from replica* as the default.
70
+
71
+
- To reduce the risk of aggressive reconnect behaviors or *connection storms*, consider setting fewer minimum connections.
72
+
73
+
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 this risk, consider using fewer connections. You can efficiently pipeline commands or batches of commands over a few connections.
74
+
75
+
- 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.
76
+
77
+
- For information about using Redisson with Java EE JCache to store HTTP session state 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).
78
+
79
+
- Use the following recommended baseline configuration for cluster mode, and modify it as needed.
0 commit comments