However, Oracle has committed to enhancing the transparency and inclusivity of the Community Edition’s development, as well as integrating functionalities that were previously exclusive to its commercial database offerings.
Oracle has officially declined to reorganize the governance of the MySQL Community Edition, a request made by a coalition of database firms offering database forks and numerous MySQL users.
This ruling follows a meeting earlier this month between Oracle and the consortium’s leading members, Percona and VillageSQL. The discussion centered on proposed alterations outlined in a February online letter, which garnered support from at least 544 individuals, including experienced database professionals, developers, and long-standing contributors.
A primary worry expressed by the signatories was Oracle’s approach to managing MySQL’s codebase updates. They contend that this management strategy has led to a notable reduction in MySQL’s market share, while competitors like PostgreSQL have gained considerably from the rising demands of AI-powered applications.
Furthermore, the letter highlighted that the limited updates provided for MySQL often lack essential features crucial for current AI-driven workloads, features that are now considered standard across the majority of databases, including Oracle’s own enterprise editions.
Those who signed the letter proposed that Oracle should transfer the open-source version of MySQL to an autonomous, non-profit foundation. This foundation would then manage roadmap development, release oversight, and access for contributors, while Oracle would still maintain ownership of its commercial MySQL products and trademarks.
Minimal Comfort Provided
Simultaneously, events occurring within Oracle’s MySQL division around the time the open letter was released failed to instill confidence among the signatories regarding the project’s sustained direction.
Among the recent job cuts was the exit of Frederic Descamps, Oracle’s MySQL community manager, who by late February had transitioned to the MariaDB Foundation.
Analysts suggest that Oracle’s decision to maintain firm control over the database is entirely predictable.
“Relinquishing control to a foundation would entail surrendering roadmap authority, which could lead to the accelerated development of features that directly rival Oracle Database, Oracle MySQL HeatWave, and Oracle’s commercial MySQL Enterprise Edition,” commented Pareekh Jain, a principal analyst at Pareekh Consulting.
By retaining management of the MySQL Community Edition, Oracle can guarantee that the open-source iteration develops in a manner consistent with its broader technological offerings,” stated Sanchit Vir Gogia, chief analyst at Greyhound Research.
Despite Oracle’s rejection of the consortium’s suggestions to hand over control, the company has pledged ongoing discussions with the MySQL community, signaling its willingness to consider input on development priorities and foster cooperation concerning the Community Edition.
“Oracle executives affirmed in a blog post: ‘This renewed commitment to openness and development speed will thrive through valuable insights and contributions from both users and contributors. The shared feedback, concepts, and experiences within this community are vital in guiding our direction and enhancing the effectiveness of our efforts. We are dedicated to sustaining an open, clear dialogue as we jointly advance and refine MySQL.'”
Revised Roadmap
With this objective, the executives revealed that Oracle intends to introduce new roadmap planning streams, concentrating on AI and cloud technologies, to expedite the introduction of developer-centric functionalities. This includes certain features previously found only in commercial versions.
Potential new inclusions under consideration encompass leveraging profile-guided optimization (PGO) for generating community binaries, incorporating a hypergraph optimizer, and improving JSON duality to streamline data manipulation language operations. Oracle also hinted at the possibility of adding vector functions but awaits further community input before making a definitive commitment.
Analysts note that while these new features and the pledge of increased openness and transparency could bolster user confidence in the Community Edition, they might present a complex challenge for providers of MySQL forks.
Jain remarked, “From one perspective, Oracle’s stricter oversight might fuel greater demand for genuine open-source MySQL alternatives, prompting users who require enterprise-level features with MySQL compatibility to opt for distributions such as Percona.”
Jain further elaborated, “Conversely, if Oracle deviates significantly or slows down the release of GPL code, fork providers will face an increasing upstream maintenance load, compelling them to allocate more resources to backporting patches or developing fundamental features independently.”
Moreover, if Oracle falls short on its stated assurances, the MySQL Community Edition will continue to lose popularity to PostgreSQL. This could eventually lead vendors like Percona to expand their support for PostgreSQL and adopt a role as database-independent specialists, thereby mitigating risks associated with the fragmentation of the MySQL ecosystem, according to Jain.
