PolarDB for MySQL Standard Edition is a new cluster type of PolarDB. This edition uses the new generation of high-performance, cost-effective computing and storage infrastructure provided by Alibaba Cloud and allows you to use the key capabilities of PolarDB at low costs.
PolarDB for MySQL Standard Edition uses a compute-storage decoupled architecture. In the architecture, PolarProxy and compute nodes are deployed on separate Elastic Compute Service (ECS) instances and the shared storage layer uses Enterprise SSDs (ESSDs) or PolarStore. This provides cost-effective storage service with high performance.
The preceding figure shows a multi-node architecture that consists of one primary node and multiple read-only nodes. If you select a node when you purchase a PolarDB for MySQL Standard Edition cluster, the cluster uses a single-node architecture. In the architecture, only a compute node can handle read and write operations.
The single-node architecture also supports PolarProxy. You can change a single-node architecture to a multi-node architecture by adding multiple read-only nodes. For more information, see Add a read-only node.
You can change a multi-node architecture to a single-node architecture by removing read-only nodes. For more information, see Remove a read-only node.
Why PolarDB for MySQL Standard Edition
PolarDB for MySQL Standard Edition uses common infrastructure, which allows you to use the key capabilities of PolarDB at low costs.
PolarDB for MySQL Standard Edition and Enterprise Edition share the same database engine. The database engine of PolarDB that has been optimized by Alibaba Cloud for years provides higher performance than open source engines.
The high-performance computing and storage infrastructure of PolarDB can significantly reduce user costs.
PolarDB decouples computing and storage resources. Each cluster consists of one primary node and multiple read-only nodes. Configuration changes and node addition can take effect within minutes.
Multiple compute nodes share storage. You are charged only for the compute nodes when you add read-only nodes. This significantly reduces scale-out costs.
PolarDB for MySQL provides clusters based on the x86 and ARM CPU architectures to meet your requirements for the two architectures.
x86: The x86 architecture is paired with Intel processors and complemented by high-performance network infrastructure. The architecture provides a comprehensive enhancement in overall performance and stability, and meets the demands of enterprise-level applications for high stability and computing power.
ARM: The ARM architecture uses Yitian 710 chips that are developed by Alibaba Cloud and 25 Gigabit Ethernet smart network interface cards (NICs) to provide strong computing power. The architecture is complemented by high-performance network infrastructure to meet the demands of public service sectors and enterprises such as Internet companies for cost-effectiveness, security, and stability of cloud services.
Scenarios
The single-node architecture of PolarDB for MySQL Standard Edition is the optimal choice for individual users who need to test and learn about database services. The architecture is suitable for startups in the early development stage of their applications.
The multi-node architecture of PolarDB for MySQL Standard Edition is suitable for large and medium-sized enterprises whose production databases need to process a large number of read requests during peak hours or perform intelligent data analysis. These enterprises include online retailers, automobile enterprises, education enterprises, and enterprise resource planning (ERP) service providers.
How to use PolarDB for MySQL
The following methods are available for managing PolarDB for MySQL clusters. You can choose one or more to perform operations like creating clusters, databases, and accounts.
Console: The PolarDB console is a friendly web-based GUI.
CLI: You can use Alibaba Cloud CLI to perform all operations that are available in the PolarDB console.
SDK: You can use SDKs to perform all operations that are available in the PolarDB console.
API: You can call API operations to perform all operations that are available in the PolarDB console.
After a PolarDB for MySQL cluster is created, you can connect to the PolarDB for MySQL cluster in one of the following ways:
DMS: You can connect to a PolarDB cluster by using Data Management (DMS) and develop databases on the web pages of DMS. For more information, see Use DMS to connect to a cluster.
Client: You can connect to a PolarDB for MySQL cluster by using common database clients, such as MySQL-Front and HeidiSQL.
Storage and data reliability
PolarDB for MySQL Standard Edition uses a shared storage architecture. This edition supports ESSDs and the PolarStore Level 4 (PSL4) and PolarStore Level 5 (PSL5) storage types.
ESSDs are ultra-high performance disks developed by Alibaba Cloud. ESSDs use a next-generation distributed block storage architecture and support 25 Gigabit Ethernet networks and Remote Direct Memory Access (RDMA). Each ESSD has low one-way latency and can deliver up to 1 million random read/write IOPS. ESSDs are provided at the following performance levels (PLs):
PL0 ESSD: A PL0 ESSD delivers the basic performance of an ESSD.
PL1 ESSD: A PL1 ESSD delivers IOPS that is five times that delivered by a PL0 ESSD and throughput that is approximately twice that delivered by the PL0 ESSD.
PL2 ESSD: A PL2 ESSD delivers IOPS and throughput that are approximately twice the IOPS and throughput delivered by a PL1 ESSD.
PL3 ESSD: A PL3 ESSD delivers IOPS that is up to ten times that delivered by a PL2 ESSD and throughput that is up to five times that delivered by the PL2 ESSD. The ESSDs are suitable for business scenarios in which highly concurrent requests must be processed with high I/O performance and at low read and write latencies.
ESSD AutoPL disk: Compared with an ESSD at one of the preceding PLs, an ESSD AutoPL disk decouples IOPS and storage, gives you the flexibility to configure IOPS and storage, and allows you to make some adjustments as needed. This reduces the overall Total Cost of Ownership (TCO).
ImportantFor more information about the performance of ESSDs, see ESSDs.
After the storage of an ESSD is exhausted, the disk is locked. In this case, the disk handles only read operations.
The following table describes the PSL4 and PSL5 storage types.
Storage type | Feature | Scenario |
PSL5 | PSL5 is the storage type used in historical versions of PolarDB and the default storage type of PolarDB clusters purchased before June 7, 2022. PSL5 provides high performance, reliability, and availability. | Business scenarios that require high performance and reliability and use databases as the core of business systems, such as the finance, e-commerce, and public service sectors, and large and medium-sized Internet services. |
PSL4 | PSL4 is a new storage type available for PolarDB. PSL4 uses the Smart-SSD technology developed in-house by Alibaba Cloud to compress and decompress data at the physical SSD level. This reduces the storage price without compromising SSD performance. | Business scenarios that prioritize cost-effectiveness. |
Data reliability
ESSDs use a distributed triplicate mechanism to ensure 99.9999999% (nine 9's) data durability. If your business is interrupted within a zone due to hardware failures, data within the zone is copied to an available disk in another zone to ensure data durability and availability. For more information, see Triplicate storage.