ApsaraDB for Redis is a database service that is compatible with open-source Redis protocols and supports hybrid storage with memory and hard disks. With reliable hot-standby master-replica architecture, various editions and series, ApsaraDB for Redis meets your requirements for high-performance, flexible and scalable key-value store.

Why Apsaradb for Redis

  • Apsaradb for Redis Community Edition supports the following functions: String, List, Set, Sorted Set, Hash, Stream, and advanced features such as transactions, message subscription, and message Publishing. The performance-enhanced series of ApsaraDB for Redis Enterprise Edition (Tair) supports other advanced data structures like TairString, TairDoc, TairHash, TairGIS and TairBloom, making it more convenient to develop Redis-based applications in certain areas.
  • Apsaradb for Redis can be stored in memory and hard disks. With RDB and AOF, Apsaradb for Redis can provide high-speed data read /write capability and meet data persistence requirements as well. The hybrid-storage series of ApsaraDB for Redis Enterprise Edition (Tair) stores all data in a hard disk, and at the same time store hot data in the memory for fast read and write operations. This helps to find the balance between performance and costs.
  • With its hardware and data deployed in the cloud, Apsaradb for Redis provides comprehensive infrastructure planning, network security protection, and system maintenance services. This allows you to focus on business innovation other than technical details of the Redis service.

Editions

Apsaradb for Redis supports two editions: Community Edition and Enterprise Edition.

Version Overview
Apsaradb for Redis Community Edition Apsaradb for Redis Community Edition is compatible with open-source Redis. It supports master-replica instances, cluster instances, and read/write-splitting instances.
ApsaraDB for Redis Enterprise Edition (Tair) ApsaraDB for Redis Enterprise Edition (Tair) is developed based on the Apsaradb for Redis Community Edition. It supports two series:
  • Performance-enhanced series, using a multi-thread model and supports several new data structure modules.
  • Hybrid-storage series, it adopts the storage mode of memory plus disk, stores all data in disk, and stores hot data in memory at the same time .

Architecture

Apsaradb for Redis supports flexible deployment architectures to meet the demands of 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 switches over to the Replica node in a matter of seconds. The master-replica architecture guarantees the high availability of system services.
Cluster master-replica instances Cluster instances run in a distributed architecture. Each data shard supports master-replica nodes to ensure high availability and automatic 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 connection mode of the cluster edition. It provides intelligent connection management to reduce application development costs.
  • Direct connect mode alows the client to bypass the proxy server and directly access backend shards to reduce network overhead and service response time. This mode of Apsaradb for Redis is suitable for services that require extremely fast response.
Read/write splitting instances Similar to the standard master-replica instances, a read/write-splitting instance uses a master-replica architecture to provide high availability. The master node is attached with read replicas for data replication, and supports linear scaling of read performance. Read replicas can effectively alleviate the performance problems caused by hotkeys. 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 supports one or three or five read replicas.
  • Read/write splitting cluster instances attach a read replica to each shard to enable automatic read/write splitting at the shard level. This type of architecture is suitable for ultra-large-scale business scenarios that require high read/write ratios.

Instance type

Apsaradb for Redis Community Edition and Enterprise Edition offer different types of spicifications. For more information, see Overview.

Scenarios

For typical scenarios, see Scenarios.