Client library-based disaster recovery

Client library-based disaster recovery for Active-Active databases using Redis client libraries with built-in failover logic.

Some Redis client libraries support geographic failover and failback. These client libraries monitor all Active-Active database members and instantiate connections for all endpoints in advance to allow faster failover and failback.

Advantages:

• No additional hardware or software components required.

• No high availability considerations.

• No scalability concerns.

• Tighter control over connectivity, such as timeouts, connection retries, and dynamic reconfiguration.

• OSS Cluster API support.

• Low latency.

Considerations:

• Requires code changes for failover and failback logic.

• Concurrent access across replicas is possible, but can be mitigated using the distributed health status provided by the database availability API requests.

• When a development framework uses Redis transparently, failover and failback might not be easy to configure.

The following diagram shows a client library-based disaster recovery approach:

The following diagram shows a client-based disaster recovery approach that also uses connection pooling:

For additional information, see the following client library guides for failover and failback:

• Jedis (Java)

• redis-py (Python)