Tair:Comparison between cloud disk-based instances and local disk-based instances

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