Is MySQL at a Crossroads? Community Weighs Forking Options Amid Oracle Uncertainty

As Oracle’s enthusiasm for managing the popular MySQL database wanes and the company recently carried out large‑scale layoffs of the MySQL core development team, contributors are questioning the project’s transparency, commitment, and long‑term direction.

Earlier this month, a group of MySQL‑interested developers convened at a database conference in San Francisco. Attendees included engineers from Percona and PlanetScale, as well as community members who rely on MySQL for their businesses and careers. They discussed the recent drop in GitHub commit activity, which many see as a sign that MySQL is being pushed into a “cold shelf”.

Vadim Tkachenko, former MySQL AB employee and now CTO of open‑source consultancy Percona, warned that MySQL is at a critical crossroads and that the community must decide whether to stay under Oracle’s umbrella or pursue alternative models, including code forks. Percona co‑founder and MySQL performance expert Peter Zaitsev likened Oracle’s handling of MySQL to “boiling a frog in warm water”, suggesting that the service’s breaking point may be reached before the community fully grasps the consequences.

PlanetScale CEO Sam Lambert emphasized MySQL’s importance to the internet and announced that PlanetScale maintains its own MySQL branch, pledging engineering resources to keep the technology healthy within an open, thriving community.

The meeting highlighted two concrete paths forward: (1) retain Oracle’s governance, or (2) create an open‑source fork. A hard fork, exemplified by MariaDB—originally created by MySQL founder Michael “Monty” Widenius in 2009 and now managed by the MariaDB Foundation—operates independently of MySQL. A tracking fork, such as Percona’s Server, stays closely compatible with upstream MySQL while adding enterprise‑grade features.

Organizers plan additional gatherings, including a Europe‑focused event in partnership with the open‑source conference FOSDEM in Brussels. They also report ongoing talks with major cloud providers and smaller cloud‑computing firms about MySQL’s future, noting that many customers are frustrated by missing features like vector search.

Historically, open‑source communities have reclaimed control by forking vendor‑linked projects; the Linux Foundation’s 2024 launch of Valkey, a fork of Redis, is cited as a recent example. The MySQL community now seeks a clear statement from Oracle on its recent actions, while continuing to explore collaborative development models.

Relevant repository: https://github.com/vitessio/vitess (Vitess, a MySQL‑based distributed database).