DCS Redis cluster instances are directly connected and compatible with the open-source Redis Cluster. Based on a decentralized cluster deployment architecture, each node in the cluster stores part of the data.
Features of Redis cluster instances:
l The smart client JedisCluster is supported.
l Compared with the active/standby specification, the overall performance is almost linearly proportional to the number of Redis shards.
Architecture Diagram
In the decentralized architecture of the Redis cluster, data storage and load processing tasks are not managed by a single central node, but are shared by multiple nodes. This architectural design aims to improve the scalability, availability and fault tolerance of the system. Data is distributed across multiple nodes, allowing for better performance and reliability.
Data Sharding
In a cluster, data sharding divides the entire data set into multiple fragments and stores them on different nodes. This sharding mechanism brings many benefits, including better horizontal scaling, load balancing, and system performance. A cluster is pre-configured with 16384 slots, and each Redis server stores the mapping relationships between all slots and the Redis server.
Features
l Data Synchronization
Maintains data consistency between the active and standby nodes of the DCS instance through incremental data synchronization.
l Automatic Active/Standby Switchover within Seconds
When the active node fails and becomes unavailable, the system automatically switches to the standby node within 30 seconds. The standby node is then upgraded to the active one and takes over business data.
l Multi-AZ Deployment
Supports multi-AZ deployment upon activation of an instance. The active and standby nodes can be deployed in different AZs. The power and network among nodes are physically isolated. When one of the AZs is unavailable, nodes in the other AZs can continue to provide services, avoiding service unavailability due to single-node faults and further improving data reliability.