ApsaraDB for Redis is a database service that is compatible with native Redis protocols and supports a hybrid storage of memory and hard disks. ApsaraDB for Redis provides a highly available hot standby architecture, and can scale to meet requirements for high-performance read/write operations.

Why ApsaraDB for Redis?

  • ApsaraDB for Redis supports multiple data types, such as strings, lists, sets, sorted sets, hash tables, and streams. It also provides other advanced features, such as transactions, and message subscription and publishing. Performance-Enhanced instances of ApsaraDB for Redis Enhanced Edition integrate with some features from Tair of Alibaba Group. These instances are also fully compatible with native Redis databases and highly suitable for some scenarios.
  • ApsaraDB for Redis provides a hybrid storage of memory and hard disks. ApsaraDB for Redis uses Redis Database (RDB) and Append Only File (AOF) to read/write data at high speed and meet data persistence requirements. Enhanced Edition instances store full data in disks and hot data in memory to guarantee high read/write performance.
  • The hardware and data of Enhanced Edition instances are deployed in the cloud. Alibaba Cloud takes care of infrastructure planning, network security and system maintenance, allowing you to focus on business development.


ApsaraDB for Redis provides Community Edition and Enhanced Edition.

Edition Overview
ApsaraDB for Redis Community Edition ApsaraDB for Redis Community Edition is compatible with the data cache of native Redis engines. It supports master-replica instances, cluster instances, and read/write-splitting instances.
ApsaraDB for Redis Enhanced Edition ApsaraDB for Redis Enhanced Edition is developed on top of Community Edition. It supports two instance types:


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

Architecture type 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 fails over to the replica node and restores services within a few seconds. This process is transparent to the user and does not affect business. The master-replica architecture ensures high availability of system services.
Cluster master-replica instances Cluster instances use a distributed architecture. Each shard works as a master-replica HA node, and provides automatic disaster recovery and failover. Multiple cluster specifications are available. You can choose a specification based on your business requirements. The cluster architecture supports two connection modes:
  • Proxy mode is the default endpoint of a cluster instance. You can configure automatic connection to reduce application development costs.
  • Direct connect mode allows the client to bypass the proxy server and directly access backend shards to reduce network overhead and service response time. It is suitable for services that require extremely fast responses.
Read/write splitting instances A read/write splitting instance uses a master-replica architecture to provide high availability. Read replicas are attached to the primary node to facilitate data replication and implement linear scaling of read performance. Read replicas can effectively alleviate the performance problems caused by hotspots. They are suitable for business scenarios that require high read/write ratios. Read/write splitting instances are classified into non-cluster instances and cluster instances.
  • A non-cluster read/write splitting instance can have one, three, or five read replicas.
  • Read/write splitting cluster instances attach a read replica to each shard to achieve automatic read/write splitting on individual shards. Read/write splitting cluster instances are suitable for ultra-large-scale business that require high read/write ratios.

Instance types

ApsaraDB for Redis Community Edition and Enhanced Edition offer different instance types for each architecture. For more information, seeOverview.


For typical scenarios, seeScenarios.