ApsaraDB for Redis instance architectures - ApsaraDB for Redis

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 instance architectures. You can click the link to an instance architecture to view details about the architecture.

Instance architecture	Architecture diagram	Scenario
Standard master-replica instances The master-replica architecture is used to ensure high availability.		Support for more native Redis features. Persistent storage on ApsaraDB for Redis instances. Stable query rate on a single ApsaraDB for Redis instance. Use of simple Redis commands, where only a few sorting and computing commands are required.
Cluster master-replica instances In the cluster architecture, each data shard runs in master-replica mode.		Large data volume. High queries per second (QPS). Throughput-intensive workloads.
Read/write splitting instances The read/write splitting architecture consists of the master and replica nodes and multiple proxy nodes.		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. To view architecture information of standard instances, see Standard master-replica instances. This rule also applies to cluster and read/write splitting instances.