Shulou(Shulou.com)05/31 Report--

What is the application scenario of Redis Cluster Edition and Redis Standard Edition? I believe many inexperienced people don't know what to do about it. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

Redis Cluster Edition-double copy

The cloud database Redis double replica cluster instance consists of three components: Proxy server (service proxy), sharding server and configuration server.

Proxy server:

For single-node configuration, there will be multiple Proxy in the cluster structure, and the system will automatically achieve load balancing and failover.

Sharding server:

Each sharding server is a double-copy highly available architecture. After the failure of the master node, the system will automatically switch between the master and the slave to ensure the high availability of the service.

Configure the server:

It is used to store cluster configuration information and partition strategy. Double-copy high availability architecture is adopted to ensure high availability.

Working with scen

Large amount of data

Redis cluster version can effectively expand the amount of data, compared with the standard version to support a larger storage capacity of 64,128,256 GB cluster version, can effectively meet the needs of data expansion.

QPS pressure is high.

The standard version of Redis cannot support a large QPS, so it is necessary to adopt a multi-node deployment method to break through the performance bottleneck of Redis single-thread. Redis Cluster Edition provides five cluster configurations of 16,32,64,128,256 GB, and provides 8-node and 16-node deployment modes. Compared to the standard version, QPS can be increased by 8 times or 16 times.

Throughput-intensive application

Compared with the standard version, the private network throughput limit of Redis cluster version is relatively loose, which can be friendly for hot data reading and large throughput services.

Applications insensitive to Redis protocol

Due to the introduction of multiple components in the architecture of the cluster version, there are some limitations in the support of the Redis protocol compared with the standard version.

Redis Standard Edition-double copy

Cloud database Redis Standard Edition-double copy mode is built in master-slave (Replication) mode. The primary node provides daily service access, and the standby node provides high availability of HA. When the primary node fails, the system will automatically switch to the standby node in 30 seconds to ensure the smooth operation of the business.

Characteristics

Reliability.

Reliable service

The dual-machine active and standby architecture is adopted, and the active and standby nodes are located in different physical machines. The master node provides external access, and users can add, delete, modify and query data through the Redis command line and the general client. When the master node fails, the self-developed HA system will automatically switch between the active and standby to ensure the smooth operation of the business.

Reliable data

The data persistence feature is enabled by default, and all data is unavailable. Data backup is supported. Users can roll back instances or clone instances for backup sets to effectively solve problems such as misoperation of data.

Compatibility

Cloud database Redis Standard Edition is developed on the basis of Redis 2.8.It is 100% compatible with Redis protocol commands. The self-built Redis database can be smoothly migrated to Redis Standard Edition. And provide data transfer tool (DTS) to carry out incremental Redis migration to ensure a smooth transition of business.

Working with scen

Services with high requirements for Redis protocol compatibility

The standard version is fully compatible with Redis protocol, and the business can be migrated smoothly.

Business used by Redis as persistent data storage

The standard edition provides persistence mechanism and backup recovery mechanism, which greatly ensures the reliability of data.

Single Redis performance pressure can be controlled

Since Redis uses a single-threaded mechanism natively, it is recommended for businesses with performance below 10w QPS. If you need higher performance requirements, choose the cluster version.

Redis commands are relatively simple, and there are few commands for sorting and computing.

Due to the single-threaded mechanism of Redis, CPU will become the main bottleneck. For businesses with more sorting and computing classes, it is recommended to choose the cluster configuration.

After reading the above, have you mastered the application scenarios of Redis Cluster Edition and Redis Standard Edition? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.