All Products
Document Center

ApsaraDB for Redis:What is ApsaraDB for Redis?

Last Updated:Jun 27, 2023

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

Why ApsaraDB for Redis?

  • ApsaraDB for Redis is a fully-managed cloud database service provided by Alibaba Cloud. The service hardware is deployed in the cloud. Alibaba Cloud provides advanced infrastructure planning, network security protection, and system maintenance. This allows you to focus on business innovation.

  • ApsaraDB for Redis supports a variety of data structures, including strings, lists, sets, sorted sets, hash tables, and streams. ApsaraDB for Redis also supports advanced features such as transactions and Pub/Sub commands.

  • ApsaraDB for Redis offers Enhanced Edition (Tair), an enterprise-level, in-memory database service that is developed based on Community Edition. Tair provides the following series types: DRAM-based instances, persistent memory-optimized instances, ESSD-based instances, and Hybrid-storage instances (phased out).

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

Instance purchase

Create an ApsaraDB for Redis instance




ApsaraDB for Redis Community Edition instance

Community Edition is a Redis-compliant, high-performance, and in-memory database service that supports master-replica, cluster, and read/write splitting architectures.

ApsaraDB for Redis Enhanced Edition (Tair)

Tair is an enhanced edition that is developed based on Community Edition. Tair provides a variety of instance series types based on storage media such as dynamic random-access memory (DRAM), non-volatile memory (NVM), and enhanced SSDs (ESSDs) to meet your requirements for low-latency access, persistence, and reduced overall costs. Tair provides higher performance, more data structures, and more flexible storage methods to meet your business requirements in different scenarios.

  • DRAM-based instances: adopt a multi-threading model, integrate a variety of features from Tair of Alibaba Group, and support a number of Tair data structures. These instances are suitable for specific scenarios.

  • Persistent memory-optimized instances: adopt persistent memory to provide large-capacity in-memory databases that are compatible with open source Redis. A persistent memory-optimized instance does not use disks for data persistence. It provides the performance that is similar to that of a Community Edition instance in terms of throughput and latency, while maintaining the persistence of each operation. This helps improve the reliability of business data.

  • ESSD-based 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 are suitable for warm and cold data storage and scenarios that require compatibility with open source Redis, large capacity, and high access performance.


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



Standard master-replica instances

Data is synchronized from the master node to replica nodes in real time. If the master node fails, workloads are failed over to a replica node. This process is automated and does not affect workloads to ensure high availability.

Cluster master-replica instances

Cluster instances use a distributed architecture. Each data shard supports the master-replica architecture to provide automatic disaster recovery and failover and ensure high availability. 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: provides intelligent connection management to reduce application development costs.

  • Direct connection mode: allows clients to bypass proxy nodes and directly access backend shards to reduce the network overhead and service response time. This mode is suitable for latency-sensitive business scenarios.

Read/write splitting instances

Read/write splitting instances use the master-replica architecture to provide high availability. Read replicas are attached to the master node to facilitate data replication and 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. The read/write splitting architecture provides two types of instances:

  • Cloud disk-based instance: Read replicas synchronize data from the master node by using star replication. You can specify up to five read replicas.

  • Local disk-based instance: Read replicas use chained replication. You can specify one, three, or five read replicas.

Instance types

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