ApsaraDB for Redis provides standard dual-replica edition and dual-replica cluster edition.

Type Description Scenario
Standalone instances A standalone instance runs in a single-node structure.
  • Cache-only applications.
    Note If your application is sensitive to data reliability, we recommend that you do not use the single-replica edition.
  • Compatibility with Redis protocols.
  • Limited queries per seconds (QPS) performance.
  • Redis commands are simple and contain few sorting and compute commands.
Master-replica instances A master-replica instance runs in a master-replica replication structure.
  • Compatibility with Redis protocols.
  • Persistent data storage based on ApsaraDB for Redis.
  • Limited QPS performance.
  • Redis commands are simple and contain few sorting and compute commands.
Standalone Cluster A standalone cluster instance is deployed in a cluster architecture. Each shard server runs in the single-node mode.
  • Large data volumes.
  • Cache-only applications.
    Note If your application is sensitive to data reliability, we recommend that you do not use the single-replica cluster edition.
  • High-QPS applications.
  • Throughput-intensive applications.
  • Cache-only applications that do not require data reliability.
Master-replica cluster A master-replica cluster instance is deployed in a cluster architecture. Each shard server runs in the master-replica mode.
  • Large data volumes.
  • High-QPS applications.
  • Throughput-intensive applications.
Read/write splitting edition A read/write splitting instance consists of the proxy servers, master and replica nodes, and read-only nodes.
  • High-QPS read requests.
  • Compatibility with Redis protocols.
  • Persistent data storage based on ApsaraDB for Redis.