Redis Introduces Client-Side Geographic Failover for Active-Active Architecture
Redis has announced the addition of client-side geographic failover capabilities to its Lettuce Java client library, complementing existing support in Jedis and redis-py. This feature enhances the Redis Active-Active architecture, which is designed for geographically distributed applications requiring real-time performance and strong eventual consistency via Conflict-Free Replicated Datatypes (CRDT). The new functionality allows client libraries to monitor multiple database endpoints and automatically switch to a healthy replica if the primary connection fails. By utilizing a circuit breaker pattern and configurable health checks, such as PING commands or REST API availability requests, the system ensures minimal disruption during outages. Users can assign weighted priorities to endpoints, directing traffic to the highest-priority available node. This update provides developers with more robust disaster recovery options alongside infrastructure-based solutions like load balancers and DNS routing. The release aims to maximize service availability for multi-region deployments by enabling seamless failover directly within the application layer, ensuring that workloads continue executing without perceived interruption when database members become unavailable.
Wire timeline
Redis Introduces Client-Side Geographic Failover for Active-Active Architecture
Redis has announced the addition of client-side geographic failover capabilities to its Lettuce Java client library, complementing existing support in Jedis and redis-py. This feature enhances the Redis Active-Active architecture, which is designed for geographically distributed applications requiring real-time performance and strong eventual consistency via Conflict-Free Replicated Datatypes (CRDT). The new functionality allows client libraries to monitor multiple database endpoints and automatically switch to a healthy replica if the primary connection fails. By utilizing a circuit breaker pattern and configurable health checks, such as PING commands or REST API availability requests, the system ensures minimal disruption during outages. Users can assign weighted priorities to endpoints, directing traffic to the highest-priority available node. This update provides developers with more robust disaster recovery options alongside infrastructure-based solutions like load balancers and DNS routing. The release aims to maximize service availability for multi-region deployments by enabling seamless failover directly within the application layer, ensuring that workloads continue executing without perceived interruption when database members become unavailable.
Redis Blog