All Products
Search
Document Center

AnalyticDB for MySQL:Editions

Last Updated:Jan 16, 2024

AnalyticDB for MySQL is available in two editions: Data Lakehouse Edition (V3.0) and Data Warehouse Edition (V3.0). This topic describes the features and specifications of different AnalyticDB for MySQL editions.

AnalyticDB for MySQL editions

Data Lakehouse Edition (V3.0)

Data Lakehouse Edition (V3.0) uses a decoupled architecture that separates computing from storage and integrates cost-effective batch processing and high-performance real-time analysis capabilities. Compared with Data Warehouse Edition (V3.0), Data Lakehouse Edition (V3.0) features fully enhanced data collection, storage, computing, and application capabilities. This edition allows you to configure data synchronization to Hudi tables on Object Storage Service (OSS) or C-Store tables in real time in a visualized manner. A single copy of data stored at the underlying storage layer is used to perform both batch processing and real-time analysis. This prevents consistency and timeliness issues that may occur in the process of data synchronization. The compute layer supports the Spark multi-language programmable compute engine that uses standardized APIs. In addition, computing resources in Data Lakehouse Edition (V3.0) are physically isolated for batch processing and real-time analysis. You can separately scale computing and storage resources based on your business requirements.

This edition is ideal for the following scenarios: data processing (such as data cleansing and standardization), multi-source aggregate analysis and table joining, and prediction and insights (such as machine learning and AI).

Data Warehouse Edition (V3.0) in elastic mode

Data Warehouse Edition (V3.0) is built on a storage-compute-decoupled architecture, and can write large amounts of data in real time and perform high-performance real-time analysis. This edition allows you to individually scale up computing and storage resources based on your business requirements. It also provides tiered storage of hot and cold data, reducing storage costs. Furthermore, computing resources are physically isolated for batch processing and real-time analysis.

This edition is ideal for writing large amounts of data in real time, performing complex extract-transform-load (ETL) operations, performing complex queries on large amounts of data, and analyzing historical data and logs.

Data Warehouse Edition (V3.0) in elastic mode is available in Basic Edition and Cluster Edition.

  • Basic Edition

    Basic Edition is deployed on a single node. It does not have the benefits of a distributed architecture. This edition supports tiered storage of hot and cold data. However, it does not support high availability, resource group isolation, or scheduled scaling. Alibaba Cloud does not provide an SLA guarantee for Basic Edition, and 4 to 8 hours are required for a failover. We recommend that you do not use Basic Edition in production environments. Basic Edition is suitable for scenarios that do not require large amounts of data, high queries per second (QPS), or high availability. It is ideal for individual developers to run tests, and startups and small enterprises to handle basic business.

  • Cluster Edition

    Cluster Edition is deployed across multiple nodes, and therefore delivers the benefits of a distributed architecture. This edition provides more powerful features to help enterprises with their development, testing, and production.

Data Warehouse Edition (V3.0) in reserved mode

Data Warehouse Edition (V3.0) is built on a storage-compute-decoupled architecture. It provides high-throughput real-time writes, high concurrency, and quick response. This edition is suitable for scenarios such as query acceleration, user portraits, interactive reports, and real-time data services.

Features

The following table compares the features of different editions.

Category

Feature

Data Lakehouse Edition (recommended)

Data Warehouse Edition

Elastic mode

Reserved mode

Computing

XIHE analytical compute engine

Supported

Supported

Supported

Spark programmable compute engine

Supported

Not supported

Not supported

Storage

XUANWU analytical storage engine

Supported

Supported

Supported

Cost-effective Hudi storage

Supported

Not supported

Not supported

Resource management

Resource group management

Supported

Supported for Cluster Edition only

Not supported

Scheduled scaling

Supported

Supported for Cluster Edition only

Not supported

On-demand scaling

Supported

Not supported

Not supported

Tiered storage of hot and cold data

Supported

Supported

Not supported

Data import

Real-time data import

Supported

Not supported

Not supported

Automatic metadata discovery

Supported

Not supported

Not supported

Job development

SQL job development

Supported

Not supported

Not supported

Spark job development

Supported

Not supported

Not supported

Job scheduling

Supported

Not supported

Note

This edition does not provide the native job scheduling capability. Job scheduling must be implemented by using Data Management (DMS) or DataWorks.

Not supported

Specifications

Specifications of Data Lakehouse Edition (V3.0)

Computing resources

Storage resources

Minimum: 16 AnalyticDB compute units (ACUs)

Maximum: 4,096 ACUs

Minimum: 24 ACUs

Maximum: 2,064 ACUs

Important

If you want to purchase more than 512 ACUs of reserved computing resources or more than 256 ACUs of reserved storage resources, submit a ticket.

Specifications of Data Warehouse Edition (V3.0) in elastic mode

Category

Computing resources

Basic Edition

8 cores and 32 GB memory, 16 cores and 64 GB memory

Cluster Edition

Minimum: 16 cores and 64 GB memory

Note

Cluster Edition clusters that are purchased in the Chinese mainland as of September 1, 2022 can be deployed across multiple nodes if they have 16 cores and 64 GB memory or 24 cores and 96 GB memory.

Specifications of Data Warehouse Edition (V3.0) in reserved mode

Instance type

Specifications

CPU

Memory (GB)

Storage (GB)

C8

24 cores

192

Minimum: 100

Maximum: 2,000

C32

96 cores

768

Minimum: 100

Maximum: 8,000

FAQ

  1. How can I view the edition of my cluster?

    Log on to the AnalyticDB for MySQL console and go to the Cluster Information page of your cluster. In the Cluster Attributes section, you can view the edition and mode of your cluster.

  2. What are the differences between Data Warehouse Edition (V3.0) in elastic mode and Data Warehouse Edition (V3.0) in reserved mode?

    • The billing methods of storage resources are different between the two modes.

      • In reserved mode, you must specify the required storage capacity 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 storage usage.

        For example, if you purchase a pay-as-you-go cluster and the storage usage on a specific day is 100 GB, the storage resources that you must pay for are calculated by using the following formula: 100 GB × Usage duration. 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 to process and compute data. Storage resources are used to read and write data. You can identify whether performance bottlenecks of your workloads are caused by computing resources or storage resources, and scale your resources accordingly to reduce costs.

  3. In what scenarios may availability be affected?

    The availability of an AnalyticDB for MySQL cluster may be affected when failures occur on the cluster or when the cluster undergoes configuration changes or version upgrades.