Oracle has formally refused to restructure control of the Community Edition of MySQL, following a request that it do so from a consortium of database companies providing forks of the database, and from MySQL users.
The decision comes after the consortium’s major players, Percona and VillageSQL, met Oracle earlier this month to discuss the changes requested in an online letter in February, which saw at least 544 users, including database veterans, developers, and long-time contributors, pledge support.
Chief among the signatories’ concerns was how Oracle has managed updates to MySQL’s codebase, which they argue has cost the database significant market share as rival PostgreSQL has profited from surges in demand from AI-driven workloads.
The letter also argued that the few updates MySQL does get don’t include features that are now table stakes for AI-driven workloads and that have become standard across most databases, including the enterprise versions offered by Oracle.
The signatories suggested that Oracle place the open version of MySQL under an independent, non-profit foundation, which in turn would oversee roadmap planning, release governance, and contributor access, while allowing Oracle to retain its commercial MySQL offerings and trademarks.
Little reassurance
Developments within Oracle’s MySQL division around the time the open letter was published also did little to reassure the signatories about the project’s long-term stewardship.
Recent layoffs there included the departure of Oracle MySQL community manager Frederic Descamps, who moved to the MariaDB Foundation at the end of February.
Oracle’s refusal to relax its control over the database is a no-brainer, according to analysts.
“Ceding governance to a foundation means ceding roadmap authority, which means potentially accelerating features that compete with Oracle Database, Oracle MySQL HeatWave, and Oracle’s commercial MySQL Enterprise Edition,” said Pareekh Jain, principal analyst at Pareekh Consulting.
Maintaining stewardship of the Community Edition of MySQL allows the company to ensure that the open-source version only evolves in ways that complement the rest of its technology portfolio, said Sanchit Vir Gogia, chief analyst at Greyhound Research.
Although Oracle rejected the consortium’s proposals to cede control, it has promised continued dialogue with the MySQL community, indicating it will remain open to feedback on development priorities and collaboration around the Community Edition.
“This renewed openness and pace of development will succeed with thoughtful input and feedback from users and contributors. The feedback, ideas, and experiences shared in this community continue to shape our direction and strengthen the impact of our work. We are deeply committed to maintaining an open, transparent dialogue as we evolve and improve MySQL together,” Oracle executives wrote in a blog post.
New roadmap
To that end, the executives said that Oracle was proposing new roadmap planning tracks centered on AI and cloud to accelerate the rollout of developer-focused capabilities, including some features that have so far remained exclusive to commercial editions.
Among the additions being explored are the use of profile-guided optimization (PGO) to create community binaries, a hypergraph optimizer, and enhancements to JSON duality designed to simplify data manipulation language operations. Oracle also suggested it might include vector functions, but is seeking additional community feedback before committing to their inclusion.
These additions and the promise of more inclusivity and transparency, while boosting confidence among users of the Community Edition, could be a double-edged sword for MySQL fork-providers, analysts say.
“On one hand, tighter Oracle control could increase demand for true open-source MySQL alternatives, as users seeking enterprise-grade capabilities with MySQL compatibility may turn to distributions like Percona,” Jain said.
“On the other hand, fork providers face a growing upstream maintenance burden if Oracle diverges further or slows the release of GPL code, forcing them to invest more in backporting fixes or building core features themselves,” Jain added.
And if Oracle fails to deliver on its promised commitments, MySQL’s Community Edition will keep losing mindshare to PostgreSQL — so much so that vendors like Percona may eventually have to broaden support for PostgreSQL and position themselves as database-agnostic experts, hedging against fragmentation in the MySQL ecosystem, Jain said.
Go to Source
Author:
