ApsaraDB for Redis is a database service that is compatible with the open source Redis protocol and supports a hybrid of memory and disks for storage. ApsaraDB for Redis provides the hot standby architecture and the cluster architecture, and can scale to meet requirements for high-throughput and low-latency operations.


  • ApsaraDB for Redis is a fully-managed cloud database service provided by Alibaba Cloud. The hardware and data of the service are deployed in the cloud. Alibaba Cloud manages infrastructure planning, network security, and system maintenance. This allows you to focus on business development.
  • ApsaraDB for Redis supports various data types, such as strings, lists, sets, sorted sets, hashes, and streams. The service also provides advanced features, such as transactions, message subscription, and message publishing.
  • ApsaraDB for Redis Enhanced Edition (Tair) is a key-value pair cloud cache service that is developed based on ApsaraDB for Redis Community Edition. ApsaraDB for Redis Enhanced Edition (Tair) provides the following series of instances: performance-enhanced instances, persistent memory-optimized instances, storage-optimized instances, and hybrid-storage instances.

For more information, see Comparison between ApsaraDB for Redis and self-managed Redis and Scenarios.

Purchase an instance

Create an ApsaraDB for Redis instance.


Edition Overview
ApsaraDB for Redis Community Edition ApsaraDB for Redis Community Edition is compatible with the data cache service of open source Redis engines. It supports master-replica instances, cluster instances, and read/write splitting instances.
ApsaraDB for Redis Enhanced Edition (Tair)

ApsaraDB for Redis Enhanced Edition (Tair) is developed based on ApsaraDB for Redis Community Edition. ApsaraDB for Redis Enhanced Edition (Tair) provides various series of instances based on storage media such as DRAM, NVM, and enhanced solid-state disks (ESSDs) to meet your requirements for low-latency access, persistence, and reduced overall costs. ApsaraDB for Redis Enhanced Edition (Tair) provides you with higher performance, more data structures, and more flexible storage methods. This helps you meet business requirements in different scenarios.

  • Performance-enhanced instances: Performance-enhanced instances adopt a multi-threading model and integrate multiple features from Tair of Alibaba Group. These instances support various Tair data structures and are suitable for specific scenarios.
  • Persistent memory-optimized instances: Persistent memory-optimized instances adopt Intel® Optane™ DC persistent memory (AEP) to provide you with in-memory databases that have a large capacity and are compatible with open source Redis. A persistent memory-optimized instance does not use disks to implement data persistence. It provides almost the same performance as an ApsaraDB for Redis Community Edition instance in terms of throughput and latency. This helps improve the reliability of business data.
  • Storage-optimized instances: Storage-optimized instances are developed based on ESSDs and are compatible with core data structures and interfaces of open source Redis. These instances can provide large-capacity, low-cost, and persistent database services. These instances apply to scenarios that store warm and cold data, and that require compatibility with open source Redis, large capacity, and high access performance.


ApsaraDB for Redis supports multiple deployment architectures that are applicable to different scenarios.

Architecture Description
Standard master-replica instances The system synchronizes data between the master node and replica node in real time. If the master node fails, the system automatically switches workloads from the master node to the replica node and restores services in seconds. This process is automatic and does not affect your business. The master-replica architecture ensures the high availability of system services.
Cluster master-replica instances Cluster instances use a distributed architecture. Each shard works as a master-replica high-availability (HA) node and provides automatic disaster recovery and failover. Multiple cluster specifications are available. You can determine the specifications based on your business requirements. The cluster architecture supports the following connection modes:
  • Proxy mode is the default connection mode of a cluster instance. This mode supports automatic connections and reduces application development costs.
  • Direct connection mode allows a client to bypass the proxy server and directly access backend shards to reduce the network overhead and service response time. This mode is suitable for business scenarios that are latency-sensitive.
Read/write splitting instances A read/write splitting instance uses the master-replica architecture to provide high availability. Read replicas are attached to the master node to facilitate data replication and implement linear scaling of read performance. Read replicas can alleviate performance issues caused by hotkeys. Read/write splitting instances are suitable for business scenarios that feature high read/write ratios. Read/write splitting instances are classified into non-cluster instances and cluster instances.
  • A non-cluster read/write splitting instance supports one, three, or five read replicas.
  • For a cluster read/write splitting instance, a read replica is attached to each shard to achieve automatic read/write splitting on individual shards. Cluster read/write splitting instances are suitable for large-scale business scenarios that feature high read/write ratios.

Instance specifications

ApsaraDB for Redis Community Edition and Enhanced Edition (Tair) provide different instance specifications for each architecture. For more information, see Overview.