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.

Benefits

  • 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, and system maintenance. This allows you to focus on business innovation.
  • ApsaraDB for Redis supports various data types, including strings, lists, sets, sorted sets, hash tables, and streams. This service also supports advanced features, such as transactions and Pub/Sub commands.
  • 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 instance series: Performance-enhanced instances, Persistent memory-optimized instances, Storage-optimized instances, and Hybrid-storage instances (phased out).

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

Purchase methods

Step 1: Create an ApsaraDB for Redis instance

Instance editions

Edition Overview
ApsaraDB for Redis Community Edition ApsaraDB for Redis Community Edition is compatible with the data cache service of open source Redis and 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 instance series based on storage media such as DRAM, NVM, and enhanced SSDs (ESSDs) to meet your requirements for low-latency access, persistence, and reduced overall costs. For more information about ESSDs, see ESSDs. ApsaraDB for Redis Enhanced Edition (Tair) provides higher performance, more data structures, and more flexible storage methods to meet your 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 highly suitable for specific scenarios.
  • Persistent memory-optimized instances: Persistent memory-optimized instances adopt Intel® Optane™ DC persistent memory (AEP) to provide large-capacity in-memory databases that 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 while maintaining persistence of each operation. 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.

Instance architectures

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

Architecture Description
Standard master-replica instances Data is synchronized from the master node to replica nodes in real time. If the master node fails, workloads are switched from the master node to a replica node. This process is automated and does not affect workloads to ensure high availability (HA).
Cluster master-replica instances Cluster instances use a distributed architecture. Each shard supports the master-replica architecture to provide automatic disaster recovery and failover and ensure HA. 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. For more information about the proxy mode, see Proxy mode.
  • Direct connection mode allows a client to bypass proxy nodes 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. For more information about the direct connection mode, see Direct connection mode.
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 available in cluster and non-cluster types:
  • 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 ultra-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.