Tair (Redis® OSS-Compatible):Comparison of cloud-native and classic instances

Item

Cloud-native instance (Recommended)

Classic instance

Architecture and scaling

Built on a new-generation control architecture that provides greater flexibility and scalability. You can quickly scale out an instance without migration if local resources are sufficient. This process is faster and has a minimal impact on your services. For more information, see Change instance configurations.

Uses a traditional control architecture. Cluster instances have defined specifications and cannot be customized. Scaling out is time-consuming.

Standard architecture

The standard architecture lets you create multi-replica instances with up to 1 primary node and 9 secondary nodes.

Supports only one secondary node.

Cluster architecture

• Eliminates the -ASK and -TRYAGAIN errors that can occur in native Redis clusters during scaling. This provides a seamless scaling experience.

• The cluster architecture lets you adjust the number of shards from 2 to 256, with a minimum granularity of a single shard. You can also adjust the specifications of shards to meet different performance and capacity requirements.

• The cluster architecture lets you create multi-replica instances. Each shard can have up to 1 primary node and 4 secondary nodes.

• Transient connections occur during scale-out.

• The number of shards for cluster instances is fixed, such as 2, 4, or 8 shards.

Read/write splitting

• Standard Edition (read/write splitting) instances allow you to adjust the number of read-only nodes from 1 to 9.

• Supports proximity-based access when read/write splitting is enabled in a multi-zone deployment.

• The cluster architecture (in proxy mode) lets you enable read/write splitting. Each shard can have up to 1 primary node and 4 read-only nodes.

• Read/write splitting architecture (discontinued) instances have a fixed number of read-only nodes: 1, 3, or 5.

Disaster recovery

If an instance is deployed across multiple zones, it supports high-availability (HA) failover within the primary zone. This prevents an increase in service access latency caused by a failover to the secondary zone. For more information, see Avoid cross-zone failovers by customizing the number of nodes.

Multi-zone instances can only fail over to the secondary zone. You must then manually switch back to the primary zone.

Instance and creation method

Supported instance types

Supported engine versions

Supported architectures

Cloud-native edition instance

Step 1: Create an instance

Redis Open-Source Edition

7.0

6.0

5.0

Standard architecture

Cluster architecture

Read/write splitting architecture

Tair (Enterprise Edition) Memory-optimized

Compatible with Redis 7.0

Compatible with Redis 6.0

Compatible with Redis 5.0

Standard architecture

Cluster architecture

Read/write splitting architecture

Tair (Enterprise Edition) Persistent Memory-optimized

Compatible with Redis 6.0

Standard architecture

Cluster architecture

Read/write splitting architecture

Tair (Enterprise Edition) Disk-based

Compatible with Redis 6.0

Standard architecture

Cluster architecture

Classic edition instance

Step 1: Create an instance

Redis Open-Source Edition

5.0

Cluster architecture

Standard architecture

Read/write splitting architecture

Tair (Enterprise Edition) Memory-optimized

5.0

Cluster architecture

Standard architecture

Read/write splitting architecture