Advantages of Cloud Database SCS for Redis

With cloud database SCS for Redis, you don't need to care about the basic OPS of the cache, such as high availability, data reliability, horizontal expansion, backup, and monitoring. You only need to pay attention to your business usage and observe whether the performance of the cloud database SCS for Redis instance is sufficient; if it is insufficient, you can consider the instance upgrade or analyze the business data with us to optimize the business.

Notices for Linking the Cloud Database SCS for Redis

The cloud database SCS for Redis instance provides two access methods, i.e., domain name and private IP access, with which the cloud database SCS for Redis instance can be accessed; however, in the case of high concurrency, it is recommended to use private IP access method to support more access capacity. Meanwhile, you don't need to worry that, in case of the backend node failure, the IP address can be changed. The private IP is a fixed IP assigned to this instance to keep balance load, and cannot be changed under any circumstances.

In general, it’s recommend that you set 3 timeout retries for Redis linking and read/write operations, which can effectively filter the impact of network jitter and bring the higher availability results for your business.

Notices for Cloud Database SCS for Redis Data Backup Risk

Generally, the main-slave nodes of Redis can provide a write data backup with high availability. At present, the day-level data snapshot backup provided by the data backup function of SCS for Redis is used to cope with the extreme faults or mis-deletion of services. Generally, you need to set a business idle time period for snapshot backup, so that it does not affect the normal read/write of the business when Redis takes a snapshot. In extreme cases, the historical data can be used for recovery of all or partial data. Before recovery, please confirm again and manually generate an up-to-date backup to avoid the data loss caused by data recovery operations.

Notices for Cloud Database SCS for Redis Instance Disk Capacity Risk

The cloud database SCS for Redis instance you purchase is only billed based on the memory usage. Redis also needs the disk space to store the persistent data. Due to the characteristics of Redis itself, enough space is reserved for your instances. However, in extreme cases, the persistent data may temporarily occupy the reserved disk space, resulting in the risk for running of the instance. It is mainly related to the write volume of your business. Thus, you should choose the product with the corresponding specifications based on the write QPS volume of your business. Generally, the cluster version can provide a larger write QPS than the standard version.

Notices for cloud database SCS for Redis failover

The cloud database SCS for Redis instance uses the high availability mode with the main-slave nodes. When the main node becomes unavailable, the automatic recovery module switches your database entry to the hot backup node within 1 minute. Therefore, you should know and configure the relinking of the business to the server in advance, preventing the business unavailability from the entry changes.