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

Benefits

  • Hardware and data are deployed in the cloud. ApsaraDB for Redis is a fully-managed cloud database service provided by Alibaba 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, hash tables, 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 an upgraded version developed based on ApsaraDB for Redis Community Edition. ApsaraDB for Redis Enhanced Edition (Tair) provides the following series of instances: Enhanced multi-threading performanceand Hybrid-storage instances.

For more information, see Comparison between ApsaraDB for Redis and on-premises Redis and Scenarios.

Editions

Edition Description
ApsaraDB for Redis Community Edition ApsaraDB for Redis Community Edition is compatible with the data cache service of native 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 Community Edition. It provides higher performance, more data structures, and more flexible storage solutions to meet your business requirements in different scenarios.

  • Performance Enhanced instances: Performance-enhanced instances provide a multi-threading model and integrate with some features from Tair of Alibaba Group. These instances are fully compatible with native Redis databases and suitable for some specific scenarios.
  • Hybrid-storage instances: Hybrid-storage instances store all data in disks and hot data in memory. This ensures high read/write performance. ApsaraDB for Redis Enhanced Edition (Tair) also uses Redis Database (RDB) and Append Only File (AOF) to perform high speed read/write operations and meet data persistence requirements.

Architectures

ApsaraDB for Redis supports multiple deployment architectures that are applicable in 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 in seconds. This process is transparent to users and does not affect your 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 select a specification based on your business requirements. The cluster architecture supports the following 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. This mode is suitable for business scenarios that are latency-sensitive.
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 alleviate performance issues caused by hot keys. Read/write splitting instances 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.
  • For a read/write splitting cluster instance, a read replica is attached to each shard to achieve automatic read/write splitting on individual shards. Read/write splitting cluster instances are suitable for large-scale business scenarios that require high read/write ratios.

Instance types

ApsaraDB for Redis Community Edition and Enhanced Edition provide different instance types for each architecture. For more information, see Overview.