What are the application scenarios of Redis Cluster Edition and Redis Standard Edition?

Redis Cluster Edition - Dual Copy

Cloud Database Redis Dual Copy Cluster Edition instance consists of three components: Proxy server (service proxy), shard server and configuration server.

• Proxy server:

  Single node configuration, there will be multiple Proxies in the cluster version structure, and the system will automatically implement load balancing and failover.

• Shard server:

  Each shard server has a dual-copy high-availability architecture. After the master node fails, the system will automatically switch between master and backup to ensure high service. Available.

• Configuration server:

  is used to store cluster configuration information and partitioning strategies. It currently uses a dual-copy high-availability architecture to ensure high availability.

Usage scenarios

• Large data volume

  Redis cluster version can effectively expand the data size, compared with the standard The version supports 64, 128, and 256 GB cluster versions with larger storage capacity, which can effectively meet data expansion needs.

• QPS is under great pressure

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

• Throughput-intensive applications

  Compared with the standard version, the intranet throughput limit of the Redis cluster version is relatively loose, and is aimed at hot data reading and high throughput types of business Can provide friendly support.

• Applications that are not sensitive to the Redis protocol

  Since the architecture of the cluster version introduces multiple components, there are certain limitations in Redis protocol support compared to the standard version.

Redis Standard Edition-Dual Copy

Double-copy mode cloud database Redis Standard Edition is built using the master-slave replication model. The master node provides daily service access, and the backup node provides HA high availability. When the master node fails, the system will automatically switch to the backup node in 30 seconds to ensure smooth business operation.

Features

• Reliability

• Reliable service

  Adopts a dual-machine active and standby architecture, with the active and standby nodes located on different physical machines. Users can access the master node through the Redis command line or a general client and perform data addition, deletion, modification and query operations. The self-developed HA system will automatically switch between active and standby when the active node fails to ensure smooth business operation.

• Data is reliable

  The data persistence function is enabled by default, and all data is written to the disk. This function supports data backup, allowing users to roll back or clone instances, thereby effectively solving problems such as data misoperation.

• Compatibility

  Redis Standard Edition is developed based on Redis2.8, and it is 100% compatible with Redis protocol commands. You can seamlessly migrate your own Redis database to Redis Standard Edition. Provides a data transfer tool (DTS) that enables Redis migration to have incremental features and ensures smooth business transition.

Usage scenarios

• Businesses with high requirements for Redis protocol compatibility

  The standard version is fully compatible with the Redis protocol, business Can migrate smoothly.

• Redis is used as a business for persistent data storage

  The standard version provides persistence mechanism and backup and recovery mechanism, which greatly ensures data reliability.

• The performance pressure of a single Redis is controllable

  It is recommended that businesses using Redis should control the QPS not to exceed 10w, because Redis uses a single-thread mechanism. If you need higher performance requirements, please choose the cluster version.

• Redis commands are relatively simple, with fewer sorting and calculation commands

  Due to the single-thread mechanism of Redis, the CPU will become the main bottleneck. For businesses with a lot of sorting and calculation types, it is recommended to use the cluster version configuration.

The above is the detailed content of What are the application scenarios of Redis Cluster Edition and Redis Standard Edition?. For more information, please follow other related articles on the PHP Chinese website!