cloud-native Data Warehouse AnalyticDB for MySQL Edition provides the following editions: the elastic mode for Cluster Edition and the reserved mode for Cluster Edition. This topic describes the differences between various editions and how to view and purchase services.

Comparison between editions

Cluster Edition
Cluster Edition provides high-performance specifications. Data can be written in real time, and quick query responses are provided. This edition applies to scenarios such as query acceleration, user profiling, interactive reports, and real-time data services. This edition supports high-throughput real-time data write and high-concurrency online query.
Elastic mode for Cluster Edition
The elastic mode for Cluster Edition separates computing resources from storage resources. It provides multiple features such as on-demand scaling, tiered storage of hot and cold data, and resource group isolation. The elastic mode for Cluster Edition is ideal for scenarios where you want to build real-time data warehouses by writing large amounts of data in real time and performing complex extract-transform-load (ETL) computing. You can also use elastic mode for Cluster Edition to implement complex queries on large amounts of data, historical data analysis, and log analysis.
The following table compares the features of different editions.
Edition Feature Performance Availability Pricing
Cluster Edition The Cluster Edition is easy to use and cost-effective, and supports multiple data sources. Clusters of the Cluster Edition can scale out nodes and scale up the storage capacity. This allows you to read and write data in real time with high throughput. The Cluster Edition supports storage separation of cold and hot data. The Cluster Edition provides 100 times the performance of MySQL databases and offers linear scalability. All data is stored in SSD disks. Compute-intensive node groups are ideal for scenarios that require high performance and high query concurrency. The Cluster Edition provides a high-availability architecture that has three replicas. Cluster upgrade and elastic scaling do not affect queries. The availability is higher than 99.95%. The price is at least USD 670 per month. Compared with offline data warehouses, this edition reduces costs by 40%.
Elastic mode for Cluster Edition Resources can be scaled on demand and on an hourly basis. You are charged based on the actual space used, which reduces resource costs. The Cluster Edition supports storage separation of cold and hot data. For a cluster in elastic mode, storage resources are decoupled from computing resources. If a Cluster Edition cluster in reserved mode and a cluster in elastic mode have the same storage and computing resources, the cluster in elastic mode provides 30% higher query performance. The elastic mode for Cluster Edition provides high-availability architecture that has three replicas and 32 cores or higher. The High-availability Edition is at least USD 839 per month.

Precautions

  • The disk space displayed on the buy page is the space size of each node group. The total disk space of a cluster equals the space size multiplied by the number of node groups.
  • The total number of scale-in, scale-out, upgrade, and downgrade operations on each database cannot exceed 12 per day.

Specifications

The following table lists the specifications of the reserved mode.
Edition Model Specifications
CPU Memory (GB) Disk space (GB)
Reserved mode for Cluster Edition C8 24 Core 192 100~1,000
C32 96 Core 768 100~8,000
The following table describes the specifications of elastic clusters.
Specification Computing resource Feature
Cluster Edition (new edition) Standalone deployment
  • 8 cores, 32 GB
  • 16 cores, 64 GB
The standalone deployment specification does not provide high availability services. It does not support resource pool isolation and time-specific scaling features. It supports the storage separation of cold and hot data feature.
Multi-machine deployment 32 cores, 128 GB at least
  • Storage and computing separation
  • On-demand time-specific scaling of resources
  • Resource pool isolation
  • Tiered storage of cold and hot data

View the edition of an AnalyticDB for MySQL cluster

  1. Log on to the AnalyticDB for MySQL console.
  2. In the upper-left corner of the page, select the region where the cluster you want to manage is deployed.
  3. In the left-side navigation pane, click Clusters.
  4. On the V3.0 Clusters tab, click the cluster ID. On the Cluster Information page, view the editions and modes in the Cluster Attributes section.

FAQ

  1. What are the differences between the elastic mode and the reserved mode?
    • The billing methods of storage resources are different in the two modes.
      • In reserved mode, you must specify the required storage capacity such as 1 TB when you create a cluster. You are charged based on the specified storage capacity.
      • In elastic mode, you do not need to specify the storage capacity when you create a cluster. You are charged based on the used storage space.

        For example, if you purchase a pay-as-you-go cluster and the used storage space is 100 GB on a particular day, the storage resources you must pay for are calculated based on the following formula: 100 GB × Service period. In elastic mode, AnalyticDB for MySQL imposes a minimum charge based on 20 GB of storage. You are charged for 20 GB of data storage even if the used storage space is less than 20 GB.

    • In elastic mode, CPU and memory resources are divided into computing resources and data resources. Computing resources are used for data processing and calculation. Data resources are used to read and write data. You can separately purchase computing resources and data resources. This helps you identify resource bottlenecks, accurately scale clusters, and reduce costs.
  2. What are the differences in service-based features between the Basic Edition and Cluster Edition?

    The Basic Edition supports all service-based features of the Cluster Edition, such as scalability (except for node groups), backup, restoration, monitoring, and alerting.

  3. What are scenarios where availability can be affected?

    The cluster availability may be affected if a cluster fails or when the cluster undergoes configuration changes or version upgrades.