Product editions

Standard Edition (Centralized)

Best suited for teams migrating from self-managed MySQL or RDS, or businesses in early growth stages that want room to scale later without re-architecting.

Built on a standalone architecture, the Standard Edition delivers 30%–40% better performance than open source MySQL while adding distributed optimizations: Paxos multi-replica for high availability and the Lizard transaction system for consistent transactions. It is 100% compatible with the MySQL ecosystem and supports finance-grade high availability (HA) with three-data-center disaster recovery within the same city and a recovery point objective (RPO) of 0.

When to choose Standard Edition:

• Your business is in its early stages with low data volume and concurrency, but you expect to scale in the future.

• You are migrating from a self-managed MySQL database or an RDS instance from another cloud provider and want better cost-effectiveness and availability.

• You require finance-grade disaster recovery with an RPO of 0.

Limitations:

• Bounded by single-node performance and capacity. The maximum specification is 90 cores.

• Keep the number of records per table between 5 million and 50 million to avoid performance degradation on large tables.

Enterprise Edition (Distributed)

Designed for production workloads that have outgrown a standalone architecture — high-concurrency traffic, very large tables, or storage that exceeds single-node capacity.

The Enterprise Edition uses a distributed architecture where compute nodes (CNs), data nodes (DNs), and a global meta service collaborate to handle distributed transactions, parallel queries, and data sharding. The cluster scales transparently to up to 1,024 nodes and petabytes of data. Like the Standard Edition, it provides finance-grade HA with three-data-center disaster recovery and an RPO of 0. It is also highly compatible with the MySQL ecosystem and supports hybrid transactional and analytical processing (HTAP) workloads through column store read-only instances.

When to choose Enterprise Edition:

• Your business faces high-concurrency bottlenecks, such as peak traffic in e-commerce transaction scenarios.

• A single table has grown very large, or total storage has exceeded the capacity of a standalone database.

• You want to replace an open source sharding solution to reduce operations and maintenance (O&M) overhead.

Limitations:

• For small specifications (CPU ≤ 32 cores), the overhead of the distributed architecture may result in slightly lower performance than the Standard Edition.

Compare editions

Instance types

Each edition provides different instance types to match your workload requirements.