PolarDB for MySQL Standard Edition is a cluster type of PolarDB built on Alibaba Cloud's high-performance computing and storage infrastructure. It delivers core PolarDB capabilities at a lower cost and uses the same database engine as PolarDB Enterprise Edition, so your existing MySQL-compatible applications, tools, and workflows connect without modification.
With PolarDB for MySQL Standard Edition, you get:
Compute-storage separation — compute nodes and shared storage scale independently, so adding read-only nodes doesn't require additional storage purchases
Elastic scaling in minutes — add or remove read-only nodes and apply configuration changes without downtime
Choice of CPU architecture — x86 (Intel) for maximum enterprise compatibility, or Arm (Yitian 710) for cost-sensitive and public-sector workloads
Flexible storage tiers — Enterprise SSDs (ESSDs) at five performance levels, or PolarStore (PSL4/PSL5) for distributed shared storage
99.9999999% (nine nines) data durability — backed by a distributed triplicate mechanism across zones
The figure above shows the multi-node architecture (one primary node plus multiple read-only nodes). If you select a single node when purchasing, the cluster uses a single-node architecture where one compute node handles all reads and writes. The single-node architecture also supports PolarProxy. To switch architectures, add a read-only node to go from single-node to multi-node, or remove a read-only node to go from multi-node to single-node.
Architecture options
PolarDB for MySQL Standard Edition uses a compute-storage decoupled architecture. PolarProxy and compute nodes run on separate Elastic Compute Service (ECS) instances, and the shared storage layer uses ESSDs or PolarStore. This separation means scale-out costs only include additional compute nodes — not storage.
Single-node vs. multi-node
| Single-node | Multi-node | |
|---|---|---|
| Best for | Development, testing, and early-stage applications | Production workloads with high read throughput or data analysis |
| Architecture | One compute node handles reads and writes | One primary node plus multiple read-only nodes |
| PolarProxy support | Yes | Yes |
| Scale-out | Add read-only nodes to convert to multi-node | Remove read-only nodes to convert to single-node |
CPU architecture options
| Architecture | Processor | Best for |
|---|---|---|
| x86 | Intel processors with high-performance network infrastructure | Enterprise applications requiring maximum stability and computing power |
| Arm | Yitian 710 chips (Alibaba Cloud) with 25 Gigabit Ethernet smart NICs | Internet companies, public sector, and cost-sensitive workloads requiring security and stability |
Use cases
Development and testing — the single-node architecture is cost-effective for individual developers and teams exploring PolarDB capabilities or building early-stage applications.
Read-heavy production workloads — the multi-node architecture suits large and medium enterprises whose databases need to handle high read traffic during peak hours. Typical industries include e-commerce, automotive, education, and enterprise resource planning (ERP).
Intelligent data analysis — the multi-node architecture suits large and medium enterprises that need to run analytical queries on their production databases.
Storage and data reliability
PolarDB for MySQL Standard Edition supports ESSDs and PolarStore (PSL4 and PSL5).
ESSDs
ESSDs are ultra-high-performance disks built on a distributed block storage architecture with 25 Gigabit Ethernet and Remote Direct Memory Access (RDMA) support, delivering up to 1 million random read/write IOPS at low one-way latency.
| Performance level | Description | Best for |
|---|---|---|
| PL0 | Baseline ESSD performance | Low-traffic workloads |
| PL1 | 5x the IOPS of PL0; ~2x the throughput | General-purpose workloads |
| PL2 | ~2x the IOPS and throughput of PL1 | High-throughput applications |
| PL3 | Up to 10x the IOPS of PL2; up to 5x the throughput | Highly concurrent, I/O-intensive workloads requiring low read/write latency |
| AutoPL | Decouples IOPS from storage capacity; configure IOPS independently | Workloads with variable performance needs; reduces total cost of ownership (TCO) |
For detailed ESSD performance benchmarks, see ESSDs. When ESSD storage is exhausted, the disk is locked and switches to read-only mode.
PolarStore
| Storage type | Description | Best for |
|---|---|---|
| PSL5 | Default storage type for clusters purchased before June 7, 2022. High performance, reliability, and availability. | Finance, e-commerce, public services, and large-scale internet applications requiring maximum reliability |
| PSL4 | Uses Alibaba Cloud's Smart-SSD technology to compress and decompress data at the physical SSD level, reducing storage costs without compromising SSD performance. | Cost-sensitive workloads |
Data reliability
ESSDs use a distributed triplicate mechanism to deliver 99.9999999% (nine nines) data durability. If hardware fails within a zone, data is automatically copied to an available disk in another zone. For details, see Triplicate storage.
Manage PolarDB for MySQL clusters
Use any of the following methods to create clusters, databases, and accounts:
Console — a web-based GUI for point-and-click cluster management
CLI — perform all console operations from the command line
SDK — integrate cluster management into your applications
API — call API operations for programmatic control
After creating a cluster, connect to it using:
Data Management (DMS) — connect and develop databases from a web browser. See Use DMS to connect to a cluster.
Database client — connect using standard MySQL clients such as MySQL-Front or HeidiSQL.