据行业最新消息，ApsaraDB RDS for MySQL 8.4: Long-Term Support, Seamless Compatibility, and Deep
By Alibaba Cloud RDS Compared with the widely adopted MySQL 8.0, MySQL 8.4 offers a longer lifecycle, greater stability, and a number of production-oriented enhancements. Recently, ApsaraDB RDS for MySQL 8.4 is available, delivering enterprise-grade high availability, high performance, and strong compatibility out of the box. If you are still running MySQL 8.0 — there is no need to rush. Although the MySQL Community Edition 8.0 reaches end of life (EOL) in April 2026, Alibaba Cloud RDS will continue to provide kernel-level maintenance for existing RDS for MySQL 8.0 instances, including security patches, critical bug fixes, and stability enhancements. You can migrate at your own pace and plan a smooth transition to 8.4 on your business timeline. If you are starting a new project or looking to adopt the most mature and reliable MySQL version available today, RDS for MySQL 8.4 is a strong choice. Here’s why. The Alibaba Cloud RDS team has completed three key areas of work around MySQL 8.4 LTS: • Extended the support window beyond the community lifecycle, so EOL is no longer an operational concern. • Taken on compatibility adaptation proactively, significantly lowering the upgrade barrier and migration costs. • Deeply integrated kernel optimizations refined over a decade of large-scale production experience at Alibaba Cloud into RDS for MySQL 8.4, delivering improvements in both performance and stability. Let’s walk through each of these in detail. The MySQL community maintains clear lifecycle policies for each major version: MySQL 5.7 reached EOL in October 2023, and community support for MySQL 8.0 ends in April 2026. After EOL, no further minor version patches are released, and the security and stability risks of running instances fall entirely on users. Alibaba Cloud RDS for MySQL’s strategy is clear and firm: proactively extend the service support window beyond the community lifecycle. During the support period, RDS for MySQL continues to release AliSQL kernel minor version updates, providing timely fixes for critical issues affecting instance security, stability, or high availability. This means that even after the community stops maintaining a version, your database is still covered. Existing MySQL 8.0 users can plan their upgrade to 8.4 at a comfortable pace without worrying about EOL. Migration to RDS for MySQL 8.4 is currently available via Data Transmission Service (DTS). In addition, a smooth in-place upgrade path from RDS for MySQL 8.0 to 8.4 is under development, which will provide a one-click, low-risk, business-transparent upgrade experience. Alibaba Cloud RDS for MySQL currently supports the following versions: 5.5, 5.6, 5.7, 8.0, and 8.4, covering both legacy deployments and future-looking workloads. Starting with MySQL 8.0, the MySQL community adopted a new release strategy with two distinct tracks: • Innovation Release: Aimed at developers experimenting with cutting-edge features; does not guarantee long-term compatibility or production-level stability (e.g., 8.1, 8.2, 8.3). • Long-Term Support (LTS): Purpose-built for production environments — a stable release designed for production use. MySQL 8.4 is the first new LTS version under this strategy. Compared with MySQL 8.0, it brings substantive improvements across query optimization, set operations, the replication ecosystem, and operational flexibility: Histograms were introduced in MySQL 8.0 as an important statistics mechanism that helps the optimizer make more accurate cost estimates for non-indexed columns, significantly influencing execution plan selection for complex queries. MySQL 8.4 adds automatic histogram updates (AUTO UPDATE): when a histogram is created with AUTO UPDATE specified, the optimizer automatically rebuilds the histogram when table data changes sufficiently, keeping statistics continuously accurate. DBAs no longer need to maintain histograms manually — one of the most valuable usability improvements in 8.4 for query optimization. MySQL 8.4 enables hash-based execution for set operations by default, significantly improving the performance of EXCEPT and INTERSECT statements. The new hash-based execution algorithm replaces the previous implementation that relied on temporary tables and is automatically applied to set operations. The set_operations_buffer_size system variable can be increased to further accelerate set operations on large datasets. This optimization works out of the box — no SQL rewrites required. MySQL 8.4 removed the SLAVE/MASTER series of replication SQL commands, retaining only the SOURCE/REPLICA commands. To facilitate data exports and replication in mixed-version environments, mysqldump adds a –output-as-version option: when exporting data from MySQL 8.4, you can specify the terminology version used in replication-related statements in the dump file, producing dump files compatible with older MySQL versions. As an LTS release, MySQL 8.4 is the first version to officially support in-place downgrades between minor versions within the same LTS series. For example, downgrading from 8.4.5 to 8.4.3 can be done by simply replacing the binary files and restarting the service — no logical export/import required, no instance rebuild needed, and downtime drops from hours to minutes. This provides a critical rollback capability for production environments. RDS for MySQL 8.4 deeply integrates battle-tested AliSQL capabilities, delivering significant advantages over the community edition in several high-frequency pain-point scenarios: The community MySQL 8.0/8.4 INSTANT DDL supports only adding and dropping columns. Modifying a column type still requires ALGORITHM=COPY. For tables of several hundreds GB of data, a single INT-to-BIGINT widening can take hours. RDS for MySQL 8.4 introduces AliSQL’s Instant Modify Column capability. The following DDL operations modify only the data dictionary metadata, require no data copy, and complete in seconds: • Integer type widening: TINYINT -> SMALLINT -> MEDIUMINT -> INT -> BIGINT• String type lengthening: CHAR(M) -> CHAR(N), VARCHAR(M) -> VARCHAR(N) (N > M) Community MySQL has multiple pain points with large transactions (deleting or updating millions of rows): binlog cache temporary file flushes blocking other write transactions, HA probe timeouts triggering unnecessary primary-secondary switchovers, and buffer pool cleanup holding locks for extended periods. RDS for MySQL 8.4 integrates all of AliSQL’s optimizations in this area, covering large transaction commit optimization, semi-synchronous replication timeout optimization, and fine-grained RTO (Recovery Time Objective) control for primary-secondary switchovers, ensuring stability and availability under large transaction workloads. Replication lag is the most common operational pain point in the MySQL ecosystem. RDS for MySQL 8.4 introduces systematic improvements across multiple layers, including DDL replication lag optimization, large transaction replication lag optimization, batch data processing replication lag optimization, and high-concurrency small transaction latency optimization, comprehensively reducing replication lag risks. Targeting kernel changes in MySQL 8.4 and typical business workloads, RDS for MySQL 8.4 delivers deep optimizations across read/write performance, write throughput, and hotspot updates. It integrates capabilities such as Binlog in Redo, Binlog Parallel Flush, and Inventory Hint, providing optimal performance across different workload profiles. Some of the hard switches in community MySQL 8.4 are unfriendly to existing 8.0 users — many monitoring scripts, operational tools, and application code still use legacy replication commands, old parameter names, and the old authentication plugin. After migrating to 8.4, these would fail outright. RDS for MySQL 8.4 takes on the compatibility adaptation work proactively: The RDS for MySQL 8.4 kernel retains the SLAVE/MASTER series of replication SQL commands and parameters. Existing scripts continue to work after upgrading to RDS 8.4 without immediate modification, giving users a generous migration window to gradually adopt the new syntax. Community MySQL 8.4 disables mysql_native_password by default, which means many applications using older client libraries and drivers would fail to connect after upgrading. RDS for MySQL 8.4 enables the mysql_native_password plugin by default, preventing connection failures caused by the upgrade. Community MySQL 8.4 changed a large number of parameter default values. RDS for MySQL adjusts parameter defaults based on operational experience and instance specifications, so users do not need to worry about the impact of MySQL 8.4 default value changes. ApsaraDB RDS for MySQL 8.4 represents a more responsible cloud database upgrade path: • On the lifecycle front, we stand behind our users — community EOL does not mean your database loses support. • On the compatibility front, we take on the adaptation work so that existing code, scripts, and tools transition smoothly. • On the kernel optimization front, we natively integrate the capabilities refined over a decade of large-scale production at Alibaba Cloud into every new release. Whether you are affected by the MySQL 5.7 or 8.0 community EOL, struggling with hotspot updates, large transactions, or replication lag, planning your next-generation core system’s database selection, or interested in MySQL 8.4’s latest features but concerned about upgrade risks — RDS for MySQL 8.4 is well suited for all of these scenarios.
业内分析认为，AI算力需求与绿色数据中心将成为行业主旋律
如果您正在寻找优质的高防服务器，欢迎访问 www.isclouder.com 了解更多