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

Tair(Redis OSS-compatible) is a database service that is compatible with the open source Redis protocol. It provides the master-replica and cluster architectures, and can scale to meet requirements for high-throughput and low-latency operations.

Why Tair（Redis OSS-compatible）?

Tair (Redis OSS-compatible) 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 protection, and system maintenance. This allows you to focus on business innovation.
Tair (Redis OSS-compatible) supports a variety of data structures, such as strings, lists, sets, sorted sets, hashes, and streams. Tair (Redis OSS-compatible) also supports advanced features such as transactions and Pub/Sub commands.
Tair (Enterprise Edition) is an in-memory database service that is developed based on Redis Open-Source Edition. Tair provides the following series types: DRAM-based instances, persistent memory-optimized instances, and ESSD/SSD-based instances.

For more information, see Comparison between Tair (Redis OSS-compatible) and self-managed Redis and Common scenarios.

Instance purchase

Step 1: Create an instance

Editions

Edition

Overview

Redis Open-Source Edition

Redis Open-Source Edition is a Redis-compliant, high-performance, and in-memory database service that supports the master-replica, cluster, and read/write splitting architectures.

Tair (Enterprise Edition)

Tair (Enterprise Edition) is an enhanced edition that is developed based on Redis Open-Source Edition. Tair provides a variety of instance series types based on storage mediums such as dynamic random-access memory (DRAM), non-volatile memory (NVM), and Enterprise SSDs (ESSDs) to meet your requirements for low-latency access, persistence, and reduced overall costs. Tair provides higher performance, more data structures, and more flexible storage methods to meet your business requirements in different scenarios.

DRAM-based instances: use a multi-threading model, integrate specific features from Tair of Alibaba Group, and support a variety of Tair data structures. These instances are suitable for specific scenarios.
Persistent memory-optimized instances: use persistent memory to provide large-capacity in-memory databases that are compatible with open source Redis. Persistent memory-optimized instances do not use disks to implement data persistence. Compared with a Redis Open-Source Edition instance, a persistent memory-optimized instance delivers almost the same throughput and latency while maintaining persistence of each operation. This helps improve the reliability of business data.
ESSD/SSD-based instances: use ESSDs or standard SSDs to store data and are compatible with the core data structures and APIs of open source Redis. An ESSD/SSD-based instance delivers approximately 60% of the performance of a Redis Open-Source Edition instance at a cost that can be as low as 15% that of a Redis Open-Source Edition instance. ESSD/SSD-based instances can provide large-capacity, low-cost, and persistent database services. These instances are suitable for warm and cold data storage scenarios that require compatibility with open source Redis, large capacity, and high access performance.

Architectures

Tair（Redis OSS-compatible） offers multiple instance deployment architectures to support a variety of scenarios.

Architecture	Description
Standard master-replica architecture	Data is synchronized from the master node to the replica node in real time. If the master node fails, workloads are failed over to the replica node. This process is automated and does not affect workloads, ensuring high service availability.
Cluster master-replica architecture	Cluster instances use a distributed architecture. Each data shard supports the master-replica architecture to provide automatic disaster recovery and failover and ensure high service availability. Multiple instance specifications are available. You can select the appropriate specifications based on business workloads and adjust the specifications as your business evolves. The cluster architecture supports the following connection modes: Proxy mode: provides intelligent connection management to reduce application development costs. Direct connection mode: allows clients to bypass proxy nodes and directly access backend shards to reduce the network overhead and service response time. This mode is suitable for latency-sensitive business scenarios.
Read/write splitting architecture	Read/write splitting instances use the master-replica architecture to provide high availability. Read replicas are attached to the master node for data replication and 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. The read/write splitting architecture provides two types of instances: Cloud-native instance: Read replicas synchronize data from the master node by using star replication. You can specify up to nine read replicas. This type is suitable for business scenarios that feature ultra-high read/write ratios. Classic instance (retired): Read replicas use chained replication. You can specify one, three, or five read replicas.

Instance specifications

Redis Open-Source Edition and Tair (Enterprise Edition) provide multiple specification options for each architecture. For more information, see Overview.