PolarDB for MySQL provides the following editions: Cluster, Single Node, and Archive Database. This topic compares the features and the applicable scenarios between the different editions.

Comparison of supported features between different editions

  • For more information about the comparison of supported features between PolarDB for MySQL 8.0, PolarDB for MySQL 5.7, and PolarDB for MySQL 5.6, see Features.
  • Features related to data migration or synchronization
    • Cluster clone (Clone a cluster)
      Edition Destination cluster
      Cluster Single Node Archive Database
      Source cluster Cluster Supported Not supported Not supported
      Single Node Not supported Supported Not supported
      Archive Database Not supported Not supported Supported
    • Cluster restoration from the recycle bin (Cluster recycle bin)
      Edition New cluster
      Cluster Single Node Archive Database
      Deleted cluster Cluster Supported Not supported Not supported
      Single Node Available soon Available soon Not supported
      Archive Database Not supported Not supported Available soon
    • Data migration from ApsaraDB RDS for MySQL (Create a PolarDB for MySQL cluster by migrating an ApsaraDB RDS for MySQL instance)
      Edition New cluster
      Cluster Single Node Archive Database
      ApsaraDB RDS for MySQL Basic Edition Available soon Available soon Not supported
      High-availability Edition Supported Not supported Not supported
      Enterprise Edition Not supported Not supported Not supported
    • Data clone from ApsaraDB RDS for MySQL (Create a PolarDB for MySQL cluster by cloning an ApsaraDB RDS for MySQL instance)
      Edition New cluster
      Cluster Single Node Archive Database
      ApsaraDB RDS for MySQL Basic Edition Available soon Available soon Not supported
      High-availability Edition Supported Supported Not supported
      Enterprise Edition Not supported Not supported Not supported
  • Specifications and resource plans
    Item Cluster Single Node Archive Database
    Specifications of compute nodes Support eight Dedicated node specifications. Supports only the node specification of 4-Core 8 GB (Burstable Performance).
    • Supports seven Archive Database (High Compression Ratio) and Archive Database Cluster Edition Dedicated dedicated node specifications.
    • Support six Archive Database Cluster Edition General-purpose general-purpose node specifications.
    Storage pricing The storage capacity in the three editions is provided based on a serverless architecture. This way, you do not need to specify the storage capacity when you purchase clusters. The storage capacity of the clusters is automatically scaled out as the volume of data increases. You are charged for the storage capacity that is consumed by the actual volume of data. On the Overview page of the cluster, you can view details about Database Storage Usage.
    • Mainland China: USD 0.00077/GB/hour.
    • China (Hong Kong) and regions outside China: USD 0.00085/GB/hour.
    Storage plan Supported
  • Transparent data encryption (TDE) (Configure TDE)
    Edition Version Support for TDE
    Cluster 5.6 The revision version must be V5.6.1.0.21 or later.
    5.7 The revision version must be V5.7.1.0.3 or later.
    8.0 The revision version must be V8.0.1.1.1 or later.
    Single Node 5.6 The revision version must be V5.6.1.0.21 or later.
    5.7 The revision version must be V5.7.1.0.3 or later.
    8.0 The revision version must be V8.0.1.1.1 or later.
    Archive Database 8.0 Not supported
    Note For information about how to check the revision version of your cluster, see Query the kernel version number.

Comparison of applicable scenarios between the different editions

Edition Description Scenarios
Single Node Edition The Singe Node Edition is developed based on a single-node architecture and uses nodes of the burstable performance type. All clusters of the Single Node Edition share the resources in a computing resource pool. This improves resource utilization and reduces resource costs because no proxy is required.

For more information, see Single Node Edition.

  • Personal learning
  • Microsites
  • Small and medium enterprises
Archive Database Edition The Archive Database Edition of PolarDB for MySQL provides a high compression ratio and uses X-Engine as the default storage engine. This edition provides a large storage capacity and allows you to store archived data at a low cost. For more information, see Overview. Business scenarios that require storage for archived data such as DingTalk messages and those that require fewer compute resources.
Cluster Edition The Cluster Edition is developed based on an architecture in which compute is decoupled from storage. This way, the edition provides faster dynamic scaling, larger storage capacity, and lower replication latency.

For more information, see Cluster Edition.

  • Production databases for large and medium-sized enterprises
  • Databases used in industries such as the Internet, IoT, e-commerce, logistics, and gaming
  • Core databases in the finance, securities, and insurance industries that require high data security

FAQ

  • Can I change the edition of my cluster?
    Yes, the edition of your cluster can be changed. The following table describes the editions to which an edition can be changed.
    Edition Destination edition
    Cluster Single Node Archive Database (High Compression Ratio) Archive Database Cluster Edition
    Source edition Cluster N/A Not supported Not supported Not supported
    Single Node Available soon N/A Not supported Not supported
    Archive Database (High Compression Ratio) Not supported Not supported N/A Supported
    Archive Database Cluster Edition Not supported Not supported Not supported N/A
  • How do the Single Node Edition and the Archive Database (High Compression Ratio) Edition ensure service availability and data reliability?

    The Single Node Edition or the Archive Database (High Compression Ratio) Edition is a database service that is used to store data for a specific purpose. Each cluster of either edition contains only one compute node. To ensure high service availability and high data reliability, new technologies, such as computing scheduling within seconds and distributed multi-replica storage are used in the Single Node Edition and the Archive Database Archive Database (High Compression Ratio) Edition.