| @@ -194,6 +194,16 @@ By default, the client now overrides the server-side dialect with version 2, aut |
|
|
| 194 |
194 |
|
| 195 |
195 |
You can find further details in the [query dialect documentation](https://redis.io/docs/latest/develop/interact/search-and-query/advanced-concepts/dialects/). |
| 196 |
196 |
|
|
197 |
+### Multi-database client (Active-Active) |
|
198 |
+ |
|
199 |
+The multi-database client allows your application to connect to multiple Redis databases, which are typically replicas of each other. It is designed to work with Redis Software and Redis Cloud Active-Active setups. The client continuously monitors database health, detects failures, and automatically fails over to the next healthy database using a configurable strategy. When the original database becomes healthy again, the client can automatically switch back to it.<br> |
|
200 |
+This is useful when: |
|
201 |
+ |
|
202 |
+1. You have more than one Redis deployment. This might include two independent Redis servers or two or more Redis databases replicated across multiple [active-active Redis Enterprise](https://redis.io/docs/latest/operate/rs/databases/active-active/) clusters. |
|
203 |
+2. You want your application to connect to one deployment at a time and to fail over to the next available deployment if the first deployment becomes unavailable. |
|
204 |
+ |
|
205 |
+For the complete failover configuration options and examples, see the [Multi-database client docs](https://redis.readthedocs.io/en/latest/multi\_database.html). |
|
206 |
+ |
| 197 |
207 |
--------------------------------------------- |
| 198 |
208 |
|
| 199 |
209 |
### Author |