DCS for Redis provides Proxy Cluster instances, which use Linux Virtual Server (LVS) and proxies to achieve high availability. Proxy Cluster instances have the following features:
- The client is decoupled from the cloud service.
- They support millions of concurrent requests, equivalent to Redis Cluster instances.
- A wide range of memory specifications adapt to different scenarios.
- A Proxy Cluster instance can be connected in the same way that a single-node or master/standby instance is connected, without any special settings on the client. You can use the IP address of the instance, and do not need to know or use the proxy or shard addresses.
Proxy Cluster DCS Redis 3.0 Instances
Proxy Cluster DCS Redis 3.0 instances are compatible with codis. The specifications range from 64 GB to 1024 GB, meeting requirements for millions of concurrent connections and massive data cache. Distributed data storage and access is implemented by DCS, without requiring development or maintenance.
Each Proxy Cluster instance consists of load balancers, proxies, cluster managers, and shards.
Total Memory |
Proxies |
Shards |
|---|---|---|
64 GB |
3 |
8 |
128 GB |
6 |
16 |
256 GB |
8 |
32 |
512 GB |
16 |
64 |
Architecture description:
- VPC
All server nodes of the instance run in the same VPC.
For intra-VPC access, the client and the instance must be in the same VPC with specified security group rule configurations.
For details, see Security Group Configurations.
- Application
The client used to access the instance.
DCS Redis instances can be accessed through open-source clients. For details about accessing DCS instances, see Accessing an Instance.
- LB-M/LB-S
The load balancers, which are deployed in master/standby HA mode. The connection addresses (IP address:Port) of the cluster DCS Redis instance are the addresses of the load balancers.
- Proxy
The proxy server used to achieve high availability and process high-concurrency client requests.
You can connect to a Proxy Cluster instance at the IP addresses of its proxies.
- Redis shard
A shard of the cluster.
Each shard consists of a pair of master/standby nodes. If the master node becomes faulty, the standby node automatically takes over cluster services.
If both the master and standby nodes of a shard are faulty, the cluster can still provide services but the data on the faulty shard is inaccessible.
- Cluster manager
The cluster configuration managers, which store configurations and partitioning policies of the cluster. You cannot modify the information about the configuration managers.