Is Oracle Killing MySQL? A Deep Dive into MySQL’s Future Under Oracle

MySQL Under Oracle: History and Myths

Peter Zaitsev, a former MySQL performance engineer, reflects on Oracle’s acquisition of Sun and MySQL and the persistent rumors that Oracle intended to kill MySQL, either by eliminating it as a competitor or by restricting it to the proprietary MySQL Enterprise edition.

In reality, Oracle has become an effective steward: the MySQL team remains largely independent under Tomas Ulin, stability and security have improved, and many technical debts have been addressed, adding features such as JSON support and advanced SQL standards.

MySQL Enterprise focuses on enterprise‑only capabilities—pluggable authentication, auditing, firewall, proprietary GUI, monitoring, and backup tools—while open‑source alternatives continue to thrive, limiting vendor lock‑in.

The “open‑source golden rule”—that a transition should not harm adoption—has guided Oracle’s approach, according to Zaitsev.

MySQL Heatwave and Emerging Limitations

Oracle’s MySQL Heatwave introduces cloud‑native features absent from the community edition, such as accelerated analytical queries and machine‑learning capabilities. However, MySQL still lacks parallel query execution, and even on machines with hundreds of CPU cores, performance gains are minimal.

This limitation affects both analytical workloads and common “GROUP BY” queries; MySQL 8 offers some parallel DDL support but not for query execution.

Other open‑source databases have added vector search and JavaScript support, areas where MySQL lags, prompting concerns that Oracle’s roadmap may be stifling MySQL’s adoption.

Comparative Landscape

According to DB‑Engines rankings, PostgreSQL has closed the adoption gap with MySQL and, based on Stack Overflow surveys, is now the most popular open‑source relational database, while MySQL’s market share declines.

Experts note that MySQL’s DBaaS focus and lack of parallel query support put it at a disadvantage compared to PostgreSQL, PgPool, ProxySQL, and MySQL Router.

Chief Technology Officer Mark Callaghan observes that the MySQL community is declining and needs external contributors to sustain development and bug fixing.

Zaitsev concludes with a warning: “Unless Oracle redirects its attention to the modern developer’s needs for relational databases, it will completely kill MySQL. If no action is taken, the result will be inaction.”