AnalyticDB for MySQL supports Elastic mode for Cluster Edition and Reserved mode for Cluster Edition. This topic describes the differences between editions and how to view and purchase services.

Editions in AnalyticDB for MySQL

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 real-time data warehouses are built by writing large amounts of data in real time and performing complex extract-transform-load (ETL) computing. You can also use the elastic mode for Cluster Edition to implement complex queries on large amounts of data, historical data analysis, and log analysis.
Reserved mode for Cluster Edition
The reserved mode for Cluster Edition provides high-performance specifications. Data can be written in real time and query response times are short. This edition is applicable to scenarios such as query acceleration, user profiling, interactive reports, and real-time data services. This edition supports high-throughput real-time data writes and high-concurrency online queries.
The following table compares the features of the two editions.
Edition Feature Performance Availability Pricing
Elastic mode for Cluster Edition Resources can be scaled on demand on an hourly basis. You are charged for the amount of space actually used, which reduces resource costs. Cold and hot data is separately stored. Storage and computing resources are separated. Elastic mode for Cluster Edition clusters that have 32 or more cores are deployed in a high-availability architecture that has three replicas. A cluster deployed in the high-availability architecture costs at least USD 841 per month.
Reserved mode for Cluster Edition The reserved mode for Cluster Edition is easy to use and cost-effective, and supports multiple data sources. Nodes and storage capacity can be flexibly scaled, which allows you to read and write data in real time with high throughput. The performance of this edition is 100 times better than that of MySQL databases. Linear scalability is provided. All data is stored in SSDs. This edition is suitable for scenarios that require high performance and high query concurrency. All reserved mode for Cluster Edition clusters are deployed in a high-availability architecture that has three replicas and provides availability of higher than 99.95%. Cluster upgrade and resource scaling do not disrupt queries. A cluster of this edition costs at least USD 892 per month. The cost of this edition is 40% lower than that of offline data warehouses.


The following table describes the specifications of the elastic mode for Cluster Edition.
Edition Specifications Description
Elastic mode for Cluster Edition Standalone deployment
  • 8 cores, 32 GB
  • 16 cores, 64 GB
The standalone deployment specification does not support high-availability, resource pool isolation, or time-specific scaling. It supports the storage separation of cold and hot data.
Multi-machine deployment
  • 32 cores, 128 GB
  • 48 cores, 192 GB
  • 64 cores, 256 GB
  • 80 cores, 320 GB
  • 96 cores, 384 GB
  • 112 cores, 448 GB
  • 128 cores, 512 GB
  • 144 cores, 576 GB
  • 160 cores, 640 GB
  • 176 cores, 704 GB
  • 192 cores, 768 GB
  • 208 cores, 832 GB
  • 224 cores, 896 GB
  • 240 cores, 960 GB
  • 256 cores, 1,024 GB
  • 272 cores, 1,088 GB
  • 288 cores, 1,152 GB
  • 304 cores, 1,216 GB
  • 320 cores, 1,280 GB
  • 384 cores, 1,536 GB
  • 416 cores, 1,664 GB
  • 448 cores, 1,792 GB
  • 480 cores, 1,920 GB
  • 576 cores, 2,304 GB
  • 640 cores, 2,560 GB
  • 768 cores, 3,072 GB
  • 800 cores, 3,200 GB
  • 896 cores, 3,584 GB
  • 960 cores, 3,840 GB
  • 1,024 cores, 4,096 GB
  • 1,120 cores, 4,480 GB
  • 1,280 cores, 5,120 GB
  • 1,440 cores, 5,760 GB
  • 1,546 cores, 6,144 GB
  • 1,600 cores, 6,400 GB
  • 1,792 cores, 7,168 GB
  • 1,920 cores, 7,680 GB
  • 2,048 cores, 8,192 GB
  • 2,080 cores, 8,320 GB
  • 2,240 cores, 8,960 GB
  • 2,400 cores, 9,600 GB
  • 2,560 cores, 10,240 GB
  • 2,880 cores, 11,520 GB
  • 3,200 cores, 12,800 GB
  • 4,000 cores, 16,000 GB
  • 4,800 cores, 19,200 GB
  • 5,600 cores, 22,400 GB
  • 6,400 cores, 25,600 GB
  • 7,200 cores, 28,800 GB
  • 8,000 cores, 32,000 GB
  • 8,800 cores, 35,200 GB
  • 9,600 cores, 38,400 GB
  • Separation between storage and computing
  • On-demand time-specific scaling of resources
  • Resource pool isolation
  • Separated storage of cold and hot data
The following table describes the specifications of the reserved mode for Cluster Edition.
Edition Model Specifications
CPU Memory (GB) Disk space (GB)
Reserved mode for Cluster Edition C8 24 cores 192 100 to 2,000
C32 96 cores 768 100 to 8,000

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 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 edition and mode of the cluster in the Cluster Attributes section.


  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.
      • When you create a cluster in reserved mode, you must specify the required storage capacity such as 1 TB. You are charged based on the specified storage capacity.
      • When you create a cluster in elastic mode, you do not need to specify the storage capacity. You are charged based on the storage usage.

        For example, if you purchase a pay-as-you-go cluster and the storage usage is 100 GB on a specific day, the storage resources that you must pay for are calculated based on the following formula: 100 GB × Usage 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 storage usage is less than 20 GB.

    • In elastic mode, computing resources are separated from storage resources. Computing resources are used for data processing and calculation. Storage resources are used to read and write data. You can separately purchase computing resources and storage resources. This helps you identify resource bottlenecks, accurately scale clusters, and reduce costs.
  2. In what scenarios may availability be affected?

    Cluster availability may be affected if failures occur in a cluster or when the cluster undergoes configuration changes or version upgrades.