The currently supported instance specifications include standard version - stand-alone, standard version - active/standby, cluster version - stand-alone, and cluster version - active/standby. You can select different specifications of instances based on your business scenarios. With the self-developed RDB+AOF persistence mechanism, all product series support data persistence, achieving high performance and data reliability.
Specifications | Supported Engine Versions | Description | Application Scenarios |
Stand-Alone | 2.8/4.0/5.0/6.0/7.0 | Single-node deployment, and supports data persistence. | ● High compatibility with the Redis protocol. ● Non-HA scenarios with small data volumes. |
Active/Standby | 2.8/4.0/5.0/6.0/7.0 | Active-standby hot backup, data persistence, and auto failover. | ● High requirements for compatibility with the Redis protocol. ● HA scenarios with small data volumes. |
Single-Node Cluster | 2.8/4.0/5.0/ | Proxy clusters, multiple data shards, and single-node deployment architecture for each shard. | ● Scenarios with large data volumes and QPS. ● Throughput-intensive application scenarios. |
Active/Standby Cluster | 2.8/4.0/5.0/ | Proxy clusters, multiple data shards, and an active-standby hot backup deployment architecture for each shard. | ● Scenarios with large data volumes and QPS. ● Throughput-intensive application scenarios. ● HA scenarios. |
Single-Node Cluster | 6.0/7.0 | Direct-connection cluster architecture, multiple data shards, and a single-node deployment architecture for each shard. | ● Scenarios with large data volumes and QPS. ● Throughput-intensive application scenarios. ● HA scenarios. |
Active/Standby Cluster | 6.0/7.0 | Direct-connect mode cluster architecture, and a leader-follower hot standby deployment architecture for each shard. | ● Scenarios with large data volumes and QPS. ● Throughput-intensive application scenarios. ● HA scenarios. |