All Products
Search
Document Center

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

Last Updated:Oct 24, 2024

When you purchase a Tair instance, we recommend that you select a cloud-native instance. This topic describes the main differences between cloud-native instances and classic instances.

Overview

Item

Cloud-native instance (recommended)

Classic instance

Architecture

Uses a new-generation management architecture that provides greater flexibility and enhanced scalability. This architecture serves as a basis for subsequent development.

Uses the conventional management architecture. Cluster instances come with predefined specifications that cannot be changed.

Scalability

  • Cloud-native instances can be quickly scaled out when local resources are sufficient. This eliminates the need to migrate to a new instance and minimizes the impact on business operations. For more information, see Change the configurations of an instance.

  • No transient connections occur when you scale out a cluster instance.

  • You can change the number of data shards in a cluster instance within the range of 2 to 256 and with a minimum step size of 1. Additionally, a data shard can be scaled up or down. This capability allows you to effectively address various requirements for performance and capacity in different scenarios.

  • You can change the number of read replicas in a read/write splitting instance within the range of 1 to 9.

  • The read/write splitting architecture supports multi-zone proximity access.

  • A scale-out consumes more time.

  • Transient connections occur when you scale out a cluster instance.

  • In a scale-out, you can only double the number of data shards in a cluster instance. For example, if the original cluster instance has two shards, you can scale the instance to four or eight shards.

  • The number of read replicas in a read/write splitting instance is fixed at 1, 3, or 5.

Feature comparison

Cloud-native instances are built on cloud-native architecture. Cloud-native instances that use the cluster architecture support imperceptible scaling. Redis embraces cloud-native architecture as the primary basis for subsequent development.

In the following table, ️️✔️ indicates that this feature is supported, ❌ indicates that this feature is not supported, and ➖ indicates that this feature is not applicable.

Differences

Category

Feature

Cloud-native instance

Classic instance

Standard architecture

Cluster architecture

Read/write splitting architecture

Standard architecture

Cluster architecture

Read/write splitting architecture

Lifecycle management

Quick scale-out

✔️

✔️

✔️

Imperceptible scaling

✔️

Adjust the number of shards for an instance

✔️

Specify a custom number of read replicas

✔️

Multi-zone proximity access

✔️

Extended features

Global Distributed Cache

✔️

✔️

✔️

All features

Category

Feature

Cloud-native instance

Classic instance

Standard architecture

Cluster architecture

Read/write splitting architecture

Standard architecture

Cluster architecture

Read/write splitting architecture

Lifecycle management

Change the configurations of an instance

✔️

✔️

✔️

✔️

✔️

✔️

Quick scale-out

✔️

✔️

✔️

Imperceptible scaling

✔️

Restart an instance

✔️

✔️

✔️

✔️

✔️

✔️

Change the billing method to subscription

✔️

✔️

✔️

✔️

✔️

✔️

Change the billing method to pay-as-you-go

✔️

✔️

✔️

✔️

✔️

✔️

Renewal

✔️

✔️

✔️

✔️

✔️

✔️

Adjust the number of shards for an instance

✔️

Specify a custom number of read replicas

✔️

Proximity access to multi-zone read/write splitting instances

✔️

Upgrade the major version

✔️

✔️

✔️

✔️

✔️

✔️

Update the minor version of an instance

✔️

✔️

✔️

✔️

✔️

✔️

Release pay-as-you-go instances

✔️

✔️

✔️

✔️

✔️

✔️

Unsubscribe from subscription instances

Manage instances in the recycle bin

✔️

✔️

✔️

✔️

✔️

✔️

Network connection management

Change the VPC or vSwitch of an instance

✔️

✔️

✔️

✔️

✔️

✔️

Apply for a public endpoint for an ApsaraDB for Redis instance

✔️

✔️

✔️

✔️

✔️

✔️

Enable the direct connection mode

✔️

✔️

Change the endpoint or port number of an instance

✔️

✔️

✔️

✔️

✔️

✔️

Bandwidth management

Enable bandwidth auto scaling

✔️

✔️

✔️

✔️

✔️

✔️

Manually increase the bandwidth of an instance

✔️

✔️

✔️

✔️

✔️

✔️

High availability management

Manually switch workloads from a master node to a replica node

✔️

✔️

✔️

✔️

✔️

✔️

Restart or rebuild proxy nodes

✔️

✔️

✔️

✔️

Upgrade proxy nodes

✔️

✔️

✔️

✔️

Parameter management

Configure instance parameters

✔️

✔️

✔️

✔️

✔️

✔️

Manage tags

Manage tags

✔️

✔️

✔️

✔️

✔️

✔️

Management of maintenance, migration, and data export

Configure a maintenance window

✔️

✔️

✔️

✔️

✔️

✔️

Migrate an instance across zones

✔️

✔️

✔️

✔️

✔️

✔️

Export the instance list

✔️

✔️

✔️

✔️

✔️

✔️

Account and security management

Create and manage database accounts

✔️

✔️

✔️

✔️

✔️

✔️

Change or reset the password

✔️

✔️

✔️

✔️

✔️

✔️

Configure whitelists

✔️

✔️

✔️

✔️

✔️

✔️

Configure an IP whitelist template

✔️

✔️

✔️

✔️

✔️

✔️

Enable TLS encryption

✔️

✔️

✔️

✔️

✔️

✔️

Enable password-free access

✔️

✔️

✔️

✔️

✔️

✔️

Enable the release protection feature for an instance

✔️

✔️

✔️

✔️

✔️

✔️

Performance monitoring

View performance monitoring data

✔️

✔️

✔️

✔️

✔️

✔️

Alert settings

✔️

✔️

✔️

✔️

✔️

✔️

View performance trends

✔️

✔️

✔️

✔️

✔️

✔️

View performance metrics in real time

✔️

✔️

✔️

✔️

✔️

✔️

Manage instance sessions

✔️

✔️

✔️

✔️

✔️

✔️

View slow queries

✔️

✔️

✔️

✔️

✔️

✔️

Use the latency insights feature

✔️

✔️

✔️

✔️

✔️

✔️

Use the offline key analysis feature

✔️

✔️

✔️

✔️

✔️

✔️

Use the real-time key statistics feature

✔️

✔️

✔️

✔️

✔️

✔️

Create a diagnostic report

✔️

✔️

✔️

✔️

✔️

✔️

Log management

Enable the audit log feature

✔️

✔️

✔️

✔️

✔️

✔️

Query slow logs

✔️

✔️

✔️

✔️

✔️

✔️

View active logs

✔️

✔️

✔️

✔️

✔️

✔️

Backup and restoration

Automatic or manual backup

✔️

✔️

✔️

✔️

✔️

✔️

Download a backup file

✔️

✔️

✔️

✔️

✔️

✔️

Use data flashback to restore data by point in time

✔️

✔️

✔️

✔️

✔️

✔️

Restore data from a backup set to a new instance

✔️

✔️

✔️

✔️

✔️️️️

✔️

Extended features

Global Distributed Cache

✔️

✔️

✔️

Use proxy query cache to address issues caused by hotkeys

✔️

✔️

✔️

✔️

Extended data structures of Tair

✔️

✔️

✔️

✔️

✔️

✔️

Multi-threading model

✔️

✔️

✔️

✔️

✔️

✔️

Supported instance series, engine versions, and architectures

Instance and its creation method

Supported instance edition and series type

Supported engine version

Supported architecture

Cloud-native instance

Create an ApsaraDB for Redis local disk-based instance

ApsaraDB for Redis Community Edition

7.0

6.0

5.0

Standard architecture

Cluster architecture

Read/write splitting architecture

Enhanced Edition (Tair) DRAM-based instances

7.0

6.0

5.0

Standard architecture

Cluster architecture

Read/write splitting architecture

Enhanced Edition (Tair) persistent memory-optimized instances

6.0

Standard architecture

Cluster architecture

Read/write splitting architecture

Enhanced Edition (Tair) ESSD/SSD-based instances

6.0

Standard architecture

Classic instance

Create an ApsaraDB for Redis instance

ApsaraDB for Redis Community Edition

5.0

4.0

Cluster architecture

Standard architecture

Read/write splitting architecture

Enhanced Edition (Tair) DRAM-based instances

5.0

Cluster architecture

Standard architecture

Read/write splitting architecture