ApsaraDB for Redis supports the standard, cluster, and read/write splitting architectures. You can select the instances suitable for your business requirements.

Architectures

The following table lists the supported architectures. You can click the architecture name to view more details.

Architecture Edition Description Scenario
Standard master-replica instances
  • Enhanced Edition
  • Community Edition
Master-replica architecture to ensure high availability
  • Support for more native Redis features.
  • Persistent storage on ApsaraDB for Redis instances.
  • Stable query rate on a single node of ApsaraDB for Redis.
  • Use of simple Redis commands, when only a few sorting and computing commands are used.
Cluster master-replica instances
  • Enhanced Edition
  • Community Edition
Uses a cluster architecture with multiple data shards. Each data shard runs in the master-replica mode and supports connections through proxy servers and internal endpoints.
  • Large data volume.
  • High queries per second (QPS).
  • Throughput-intensive workloads.
Read/write splitting instances
  • Enhanced Edition
  • Community Edition
Consists of multiple proxy servers, one master node, one replica node, and one or more read replicas.
  • High QPS.
  • Support for more native Redis features.
  • Persistent storage on ApsaraDB for Redis instances.

Documentation applicability

You must understand the following concepts in ApsaraDB for Redis: architectures, editions such as Community Edition and Enhanced Edition, series types such as performance-enhanced instances, and engine versions such as Redis 4.0 or 5.0. The descriptions and topics listed in the preceding table are applicable to related editions, series types, and engine versions. For standard instances, you can view architecture information in Standard master-replica instances. This rule also applies to cluster instances and read/write splitting instances.