Tair (Redis® OSS-Compatible):What is Tair (Redis OSS-compatible)?

Instance edition

Description

Redis Open-Source Edition

A high-performance in-memory database product compatible with Redis, supporting standard (master-replica), cluster, and read/write splitting architectures.

Tair (Enterprise Edition)

Tair (Enterprise Edition) is an enhanced Redis service developed based on Redis Open-Source Edition, designed around the three core dimensions of access latency, persistence requirements, and overall cost. It offers a variety of product forms based on storage media such as dynamic random-access memory (DRAM), non-volatile memory (NVM), and enterprise SSDs (ESSDs) to provide better performance, more data structures, and more flexible storage methods to meet diverse business needs.

• DRAM-optimized: Uses a multi-threaded model, integrates some features of Alibaba Cloud Tair, and supports Tair data structures, making it ideal for certain business scenarios.

• Persistent memory-optimized: Based on persistent memory technology, it provides a large-capacity, Redis-compatible in-memory database product. Data persistence does not rely on traditional disks, ensuring that each operation is persisted while delivering throughput and latency comparable to Redis Open-Source Edition, significantly improving data reliability.

• ESSD/SSD-based: Developed based on ESSD and SSD, it is compatible with core Redis data structures and interfaces. Its cost is as low as 15% of Redis Open-Source Edition, with performance at about 60% of Redis Open-Source Edition. It can provide a large-capacity, low-cost, and highly durable database service, ideal for warm/cold data storage scenarios that require Redis compatibility, high capacity, and moderate access performance.

Architecture

Description

Standard architecture

Data is synchronized in real time between the master node and the replica. If the master node fails, the system automatically fails over to the replica. The entire process is automatic and has no impact on your business, ensuring high availability (HA).

Cluster architecture

Cluster instances use a distributed architecture where each data shard supports master-replica failover. It automatically performs failover to ensure high availability. It also provides a variety of specifications, allowing you to choose the appropriate one based on your business load and freely scale as your business grows. Instances using the cluster architecture support two connection modes:

• Proxy mode (recommended): Provides intelligent connection management to reduce application development costs.

• Direct connection mode: Clients bypass the proxy server and access the backend data shards directly. This can reduce network overhead and service response time, making it ideal for applications with stringent Redis response time requirements.

Read/write splitting

Read/write splitting instances achieve high availability through a master-replica architecture. The master node mounts read replicas to achieve data replication and supports linear scaling of read performance. Read replicas can effectively mitigate performance issues caused by hot keys and are ideal for read-heavy workloads. Two versions of read/write splitting instances are available.

• Read/write splitting (cloud-native edition): All read replicas synchronize data from the master node in a star-shaped replication topology. It supports a customizable number of read replicas (1 to 4 per shard in a cluster architecture, and 1 to 9 in a standard architecture), making it suitable for large-scale, high-read-ratio business scenarios.

• Read/write splitting (classic edition, discontinued): Read replicas use a chain replication architecture. It supports configuring 1, 3, or 5 read replicas.