Identifying Requirements

Before purchasing a DCS instance, identify your requirements:

1. Decide on the instance type.

   DCS provides single-node, master/standby, Proxy Cluster, and Redis Cluster types of instances. For details about the instance architectures, see DCS Instance Types.

2. Decide on the required instance specification.

   Each specification specifies the maximum available memory, number of connections, and bandwidth. For details, see DCS Instance Specifications.

3. Decide on the region and whether cross-AZ deployment is required.

   Choose a region closest to your application to reduce latency.

   A region consists of multiple availability zones (AZs) with physically isolated power supplies and networks. Master/standby and cluster DCS instances can be deployed across AZs. Applications can also be deployed across AZs to achieve high availability (HA) for both data and applications.

   

   • If a master/standby or cluster DCS instance is deployed across AZs, faults in an AZ do not affect cache nodes in other AZs. This is because when the master node is faulty, the standby cache node will automatically become the master node to provide services. Such deployment achieves better disaster recovery.
   • Deploying a DCS instance across AZs slightly reduces network efficiency compared with deploying an instance within an AZ. Therefore, if a DCS instance is deployed across AZs, synchronization between master and standby cache nodes is slightly less efficient.
4. Decide whether backup policies are required.

   Currently, backup policies can be configured only for master/standby, Proxy Cluster, and Redis Cluster DCS instances. For details about backup and restoration, see Overview.