This topic describes the release history of PolarDB and the links to corresponding topics.
|Read/write splitting available for Global Database Network||The read/write mode can be set to Read and Write (Automatic Read-write Splitting) for all the cluster endpoints in the Global Database Network (GDN) of PolarDB for MySQL. Read requests are sent to the on-premises secondary cluster, and write requests are automatically forwarded to the primary cluster in the central region. The central region indicates the region where the primary cluster resides.||2020-07-01||Create a GDN and a secondary cluster|
|Switch with endpoints interchange (connection changes not required)||The Switch with Endpoints Interchange (Connection Changes not Required) option is available when you upgrade an ApsaraDB RDS for MySQL instance to a PolarDB for MySQL instance. If you select this option, the system automatically exchanges the endpoint of the ApsaraDB RDS for MySQL instance and the endpoint of PolarDB for MySQL instance. You do not need to modify the connection configurations and code of your applications.||2020-06-10||Create a PolarDB for MySQL cluster from an ApsaraDB RDS for MySQL instance|
|Upgraded backup feature||PolarDB provides more advanced configurations and capabilities for the backup feature to meet enterprise-level data backup requirements. This ensures data security.||2020-05-12||Back up data|
|Backup feature available for sale||You are charged for the storage space occupied by backup files and log files. PolarDB provides a limited quota of free storage space.||2020-05-12||[Notice] Alibaba Cloud begins charging for backups|
|Database release in the Japan (Tokyo) region||PolarDB for MySQL is available in the Japan (Tokyo) region.||2020-04-30||Create a PolarDB MySQL cluster|
|Release of PolarDB for MySQL in the China (Chengdu) region||PolarDB for MySQL is available in the China (Chengdu) region.||2020-04-13||Create a PolarDB MySQL cluster|
|Release of PolarDB for MySQL in the US (Virginia) region||PolarDB for MySQL 5.6 and 8.0 are available in the US (Virginia) region.||2020-03-09||Create a PolarDB MySQL cluster|
|Global consistency||PolarDB for MySQL cluster endpoints support global consistency. The latest data can be retrieved, if a delay occurs when data is copied from a primary node to read-only nodes.||2020-03-03|
|SSL encrypted transmission||The primary endpoint of PolarDB for MySQL supports Secure Sockets Layer (SSL) encrypted transmission. SSL encrypts network connections at the transport layer. This improves data security and integrity, but increases the network response time. You can enable SSL encryption based on your business needs.||2020-02-11||Configure SSL encryption|
|Offload reads from the primary node||PolarDB for MySQL supports the Offload Reads from Primary Node feature. SQL query requests are sent to read-only nodes while data consistency is ensured. This reduces the workloads of primary nodes and maintains the stability of primary nodes.||2020-02-07||Modify and delete a cluster endpoint|
|New alert rules||The new alert rule feature (POLARDB MYSQL CLUSTER) is available on CloudMonitor. This
feature allows you to create alert rules based on more performance metrics, which
delivers improved user experience in alerting and notifications.
We recommend that you use new alert rules for improved user experience.
|2020-01-09||Create an alert rule|
|Support for diagnostics and optimization features in more regions||The diagnostics and optimization features of PolarDB for MySQL are available in the
US (Silicon Valley) and Germany (Frankfurt) regions.
The diagnostics and optimization features include:
|Release of PolarDB for MySQL in the Malaysia (Kuala Lumpur) region||PolarDB for MySQL 5.6 and 8.0 are available in the Malaysia (Kuala Lumpur) region.||2019-11-14||Create a PolarDB MySQL cluster|
|Support for data migration across zones||PolarDB for MySQL allows you to change the primary zone. You can use this feature to migrate the compute nodes in your PolarDB cluster to other zones. This feature can be used for disaster recovery or to meet the requirement that an ECS instance accesses a PolarDB cluster from a nearby zone.||2019-11-13||Deploy a cluster across multiple zones and change the primary zone|
|API operations for performance monitoring||
|Release of storage plans for CloudTmall (new retail cloud)||Nine types of storage plans are available. These storage plans can be used to store
100 GB to 100 TB data. You can upgrade storage plans at any time based on your business
|Support for the configuration of node failover priorities||PolarDB allows you to configure node failover priorities. By default, the priority of each node is 1. You can specify an integer from 1 to 15 as the priority. The configuration takes effect immediately without affecting database services.||2019-10-14||-|
|Failover||PolarDB provides the failover feature. You can switch the services of the primary node to a specified read-only node based on your business needs.||2019-10-14||Switch over services between primary and read-only nodes|
|Commercial use of PolarDB for MySQL 8.0||PolarDB for MySQL 8.0 supports parallel queries. In the scenario of TPC-H testing, PolarDB for MySQL 8.0 can reduce the query time by 10 times when compared with the previous version. You can add fields without locking tables, which reduces the negative impact on service stability. PolarDB for MySQL 8.0 optimizes the features of NoSQL databases, supports JSON data types, and provides SQL window functions.||2019-09-12||Parallel query|
|Commercial use of PolarDB||PolarDB is available for commercial use in the following nine regions:
||2019-09-05||Overview of Apsara PolarDB|
|Release of PolarDB in the Indonesia (Jakarta) region||PolarDB is available in the Indonesia (Jakarta) region.||2019-08-20||Overview of Apsara PolarDB|