ApsaraDB for Redis supports the standard, cluster, and read/write splitting architectures. You can select an architecture that suits your business requirements.

Architectures

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

ArchitectureEditionOverviewScenario
Standard master-replica instances
  • Enhanced Edition (Tair)
  • Community Edition
The standard architecture adopts the master-replica deployment type 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, where only a few sorting and computing commands are required.
Cluster master-replica instances
  • Enhanced Edition (Tair)
  • Community Edition
The cluster architecture contains multiple data shards. Each data shard runs in master-replica mode.
  • Large data volume.
  • High queries per second (QPS).
  • Throughput-intensive workloads.
Read/write splitting instances
  • Enhanced Edition (Tair)
  • Community Edition
The read/write splitting architecture consists of multiple proxy nodes, 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 (Tair), series types such as DRAM-based 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 and read/write splitting instances.