MySQL 8.4.0 was released on April 30, 2024, beginning the MySQL 8.4 Long Term Support series. Oracle’s official release history confirms this milestone. For organizations running websites and business applications, an LTS release provides a basis for maintenance planning. Choosing a destination still requires a clear understanding of the application, its dependencies and the support arrangements involved.
Start with what the business needs to preserve
A database change affects more than stored tables. A shop must save an order correctly; a booking system must keep its availability consistent; an internal application must produce the expected reports. List those outcomes before selecting a migration method. Record who can confirm each result and which errors would require stopping the transition.
Inventory the actual database product and version, application framework, connectors and third-party integrations. Check the documented upgrade path for that starting point and the destination’s platform requirements. Oracle’s upgrade-path documentation explains why a major release should not be treated as an unrestricted jump from any older installation. Release notes and application-vendor requirements should inform the decision.
Test the workload, not just the connection
Oracle’s upgrade guidance recommends compatibility checks, application testing, performance comparison and a usable backup. An automated checker is valuable, but it does not confirm that a customer journey or an accounting export still behaves as intended.
- Use an appropriately protected test environment with representative data and access rules.
- Exercise important reads and writes, reports, imports and scheduled work.
- Compare results and response times with a baseline, including less frequent business tasks.
- Define recovery steps and who approves the move before changing production.
Authentication, SQL behavior and removed settings can affect older applications. Resolve the relevant compatibility issue instead of assuming that a successful server startup proves readiness. The migration plan should also explain how new business data will be handled if the transition has to stop or recovery becomes necessary.
Keep MySQL and MariaDB decisions distinct
MySQL and MariaDB are separate products. MariaDB’s compatibility documentation identifies differences in authentication, data behavior and replication. Moving between them needs its own compatibility and data-transfer assessment. A similar command name or shared history does not make the move equivalent to an ordinary MySQL update.
Nuagerie’s cloud management services can help frame infrastructure planning around these application requirements. Describe the database project you are considering, including the product in use, application dependencies, acceptable change window and available vendor support. We can help define the assessment, testing and coordination needed before choosing the implementation.
