All Products
Search
Document Center

ApsaraDB for Redis:Comparison between cloud disk-based instances and local disk-based instances

Last Updated:Mar 04, 2024

When you purchase ApsaraDB for Redis instances, you can select local disk-based or cloud disk-based instances to meet the requirements of different business scenarios. This topic compares these two types of instances.

Overview

Item

Cloud disk-based instance (recommended)

Local disk-based instance

Architecture

Uses the new-generation management architecture that offers 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 disk-based instances provide higher scalability than local disk-based instances.

  • 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.

  • 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 disk-based instances are built on cloud-native architecture. Cloud disk-based 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

Classic (local disk-based) instance

Cloud-native (cloud disk-based) instance

Standard architecture

Cluster architecture

Read/write splitting architecture

Standard architecture

Cluster architecture

Read/write splitting architecture

Lifecycle management

Adjust the number of shards for an instance

✔️

Specify a custom number of read replicas

✔️

Bandwidth management

Enable bandwidth auto scaling

✔️

✔️

✔️

Extended features

Global Distributed Cache

✔️

✔️

✔️

All features

Category

Feature

Local disk-based instance

Cloud disk-based 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

✔️

✔️

✔️

✔️

✔️

Supports 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

✔️

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 a proxy node

✔️

✔️

✔️

✔️

Upgrade proxy nodes

✔️

✔️

✔️

✔️

Parameter management

Configure instance parameters

✔️

✔️

✔️

✔️

✔️

✔️

Tag management

Create tags

✔️

✔️

✔️

✔️

✔️

✔️

Management of maintenance, migration, and data export

Set a maintenance window

✔️

✔️

✔️

✔️

✔️

✔️

Migrate an instance across zones

✔️

✔️

✔️

✔️

✔️

✔️

Export the instance list

✔️

✔️

✔️

✔️

✔️

✔️

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

✔️

✔️

✔️

✔️

✔️

✔️

Performance trends

✔️

✔️

✔️

✔️

✔️

✔️

View performance metrics in real time

✔️

✔️

✔️

✔️

✔️

✔️

Manage instance sessions

✔️

✔️

✔️

✔️

✔️

✔️

Slow queries

✔️

✔️

✔️

✔️

✔️

✔️

Latency insights

✔️

✔️

✔️

✔️

✔️

✔️

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 ApsaraDB for Redis Enhanced Edition (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

Local disk-based instance

Create a local disk-based 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

Cloud disk-based instance

Create an ApsaraDB for Redis cloud 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

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-based instances

4.0

Standard architecture