Oracle has brushed aside an outreach from the open-source database community seeking more cooperative support for the MySQL project.
Many long-time MySQL contributors, engineers, and ecosystem leaders publicly voiced their support in an open letter inviting Oracle to discuss establishing a vendor-neutral foundation for the MySQL ecosystem.
Open-source database software services firm Percona and innovation platform developer VillageSQL met with Oracle officials on March 5 to present the letter and discuss cooperative options, to no avail. VillageSQL is the innovation platform for MySQL, a drop-in replacement with extensions for the agentic AI era.
The letter, signed by more than 500 supporters, including many former Oracle contributors and database leaders across the industry, outlined growing concerns around governance, transparency, contribution barriers, and long-term sustainability. It proposed three potential governance models designed to strengthen MySQL’s future while explicitly recognizing Oracle’s ownership of the software and trademark.
The proposal reflects growing concern among developers and vendors that MySQL’s long-term innovation could suffer without broader community participation in its governance.
“While Oracle officials declined to be involved, they reiterated their commitment to transparency and community engagement. We will continue to maintain open conversations and encourage participation in the public discussion forums they are hosting,” Vadim Tkachenko, co-founder and technology fellow at Percona, told LinuxInsider.
Oracle officials also did not respond to our request for comment.
Transparency and Collaboration Concerns
Since Oracle acquired MySQL in 2010, many in the ecosystem believe MySQL’s development model has become less transparent and collaborative than it was during its early open-source era, according to Tkachenko.
He explained that over time, concerns have grown around slower upstream development velocity, limited external participation in roadmap decisions, and delayed integration of community contributions. As a result, innovation has increasingly shifted outside the core upstream project.
“These concerns have escalated over the last four years, as Oracle’s primary focus became HeatWave, while MySQL Community was left neglected,” he said.
Percona has long advocated for a stronger, more transparent MySQL ecosystem and previously called for improvements in MySQL’s stewardship and community infrastructure. The company said it would align its resources with whichever governance model best fits Oracle’s current roadmap.
MySQL, a widely deployed relational database management system, has seen its standing in the open-source community shift significantly, marked by stagnant community-driven development and a pivot toward corporate-controlled, proprietary, or cloud-native features. Still a cornerstone of established web applications such as the LAMP stack, MySQL is increasingly being replaced by competitors like PostgreSQL in new development, according to Percona.
Technical and Governance Challenges
Tkachenko noted that, from a technical perspective, many in the community feel that MySQL is falling behind in areas increasingly considered table stakes for modern workloads. For example, capabilities such as native vector search for AI and machine learning use cases are not yet available in upstream MySQL, whereas other database ecosystems are moving quickly to support these workloads.
He added that there is a broader perception that development resources have shifted toward cloud-specific implementations. In particular, the shift appears to be toward Oracle’s managed offerings on Oracle Cloud Infrastructure.
“That leaves the open-source edition of MySQL progressing more slowly than many in the ecosystem would like,” Tkachenko said.
Beyond specific features, the challenge lies in governance and collaboration. External contributors have limited visibility into roadmap decisions and the prioritization of community contributions.
“That dynamic makes it harder for the broader ecosystem to coordinate development and invest confidently in the future of the platform,” he said.
What Fragmentation Means for MySQL
Tkachenko warned that the MySQL ecosystem risks becoming increasingly difficult to navigate.
Fragmentation for users and enterprises can create confusion around compatibility, migration paths, and long-term support. Organizations may believe they are running MySQL, but in reality they may be operating on different forks or cloud-specific implementations with varying behaviors and feature sets.
“For contributors and vendors, fragmentation makes collaboration harder. Development efforts become duplicated across projects rather than strengthening a shared upstream platform,” he added.
Over time, this can slow overall progress and make it harder to establish a clear, widely trusted foundation for the ecosystem.
Mixed Messages From Oracle Challenge User Retention
Tkachenko acknowledged that the lead-up to the outcry for an open letter to Oracle had already contributed to MySQL’s loss of prominence. He had hoped that Oracle would be more receptive to resolving its developmental issues.
“New features, performance improvements, and operational tooling are often developed in forks or cloud-managed variants rather than within upstream MySQL itself,” he said.
This shift has weakened MySQL’s position as the central innovation hub of its ecosystem and prompted calls for clearer governance and more open collaboration to restore momentum. Many contributors and enterprise users now view MySQL as no longer a fast-moving, community-driven open-source project. Instead, it has come to be viewed as a mature, stable, but slower-moving corporate-owned product.
The endgame? It will likely remain in production for years due to its legacy. But many new projects are increasingly selecting alternative databases.
Loading ...
