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.
- 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 a variety of 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 an in-memory database service that is developed based on ApsaraDB for Redis Community Edition for enterprises. 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.
|ApsaraDB for Redis Community Edition||ApsaraDB for Redis Community Edition is compatible with the high-performance in-memory database 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 a variety of 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.
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 switched from the master node 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 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
|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 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:
ApsaraDB for Redis Community Edition and Enhanced Edition (Tair) provide different instance specifications for each architecture. For more information, see Overview.