When Oracle Drops the Ball: Why MariaDB is the Future of the MySQL World

The news has circulated quietly in industry corners, but the implications are far too significant to brush aside: Oracle seems to have ended the Open Source era of MySQL.

I am not a spokesperson for Oracle, yet the signs are unmistakable. Entire teams associated with MySQL at Oracle have been dissolved, spanning engineering, development and sales. On LinkedIn, I’ve received a wave of messages from former colleagues — both long-time MySQL veterans and those who joined Oracle years after MariaDB was founded in 2009.

The impression is clear: Oracle has made a rational business decision to pivot towards AI and cloud, where MySQL only matters insofar as it strengthens OCI and Heatwave. Beyond that, the database that once defined Open Source relational technology is no longer strategic.

A rational choice for Oracle, a disaster for the ecosystem

From a shareholder perspective, this may even look elegant. If MySQL users migrate to OCI, so much the better. If they don’t, Oracle’s revenue streams are not critically harmed.

But for the wider ecosystem — developers, distribution maintainers, application builders, enterprises — this is a seismic event. Who wants to build for a tool that no longer evolves?

The real meaning of “end of life”

Databases, unlike trendy frameworks, are slow-moving technology. There is no urgent need to migrate away tomorrow. Existing systems will keep running for years.

Yet “end of life” suddenly takes on a concrete meaning. The right question is no longer “if” but “when” to start planning for life after MySQL.

MariaDB: a vision born fifteen years ago

When MariaDB was created 15 years ago, it was not merely a clone. It was designed to go beyond the constraints that held MySQL back — to provide an enterprise-class, general-purpose relational database with no ownership shackles limiting its roadmap.

Performance, stability, ease of use: these values were inherited from MySQL, but MariaDB’s founders added another principle — independence. A Foundation-led governance model ensures alignment with users, not with the quarterly priorities of a single vendor.

A safety net, ready from day one

The MariaDB founders also had a second motivation: what if Oracle did not support MySQL forever? What if, someday, MySQL’s Open Source soul was deprioritised?

That safety net was always part of the vision. MariaDB would be there — compatible, supported, and open.

Think of MySQL users as passengers on the Titanic. MariaDB is not a distant ship on the horizon. It is a vessel close by, with ropes and ladders lowered, ready for people to climb aboard. Other boats exist, but they are further away and harder to reach.

More than a replacement: an upgrade

The safety-net metaphor is useful, but it risks underplaying the reality. MariaDB is not simply the fallback option. It is an upgrade.

From advanced compatibility modes with Oracle Database, to high-availability maturity, to avoiding legacy limitations such as vacuuming, and to MariaDB Vector AI capabilities, MariaDB is already ahead.

Equally important are the business dimensions: a licensing model that prevents the spread of closed-source extensions, and a governance model that can set and deliver on a roadmap aligned with user needs.

Planning for life after MySQL

So what should organisations do today? Begin charting a path.

• Migration strategy: test workloads on MariaDB, identify any potential compatibility quirks.
• Skills strategy: connect with the pool of MySQL engineers now leaving Oracle — their expertise is invaluable.
• Risk strategy: treat MariaDB as a low-friction upgrade, not a costly replatforming exercise.

“Perception versus reality”: the MariaDB Foundation board’s view

At the recent MariaDB Foundation board meeting, the discussion on the demise of MySQL was frank.

• Jignesh Shah of Amazon AWS noted that many users perceive a larger gap between MySQL and MariaDB than actually exists. A compatibility flag could help bridge this perception.
• Sergei Golubchik, the architect part of MySQL/MariaDB since last century, confirmed that technical differences are rare and easily managed.
• Steve Shaw of HammerDB insisted that MariaDB must be framed as an upgrade, not “just” a replacement.
• Eric Herman added that transparency is vital: migrations must be predictable, with rollback options.
• Frank Karlitschek of NextCloud reminded us that perception is shaped by storytelling, and called for more visible case studies of successful migrations.

The board was united: MariaDB is not merely filling a vacuum. It is building the future that MySQL users were once promised.

The conclusion: MariaDB is the replacement for MySQL

We began with the question: is MariaDB a replacement for MySQL?
Steve Shaw’s answer is sharper: MariaDB is an upgrade.

And yet, in the context of Oracle’s abandonment of MySQL’s Open Source soul, the message must be clear. MariaDB is the replacement for MySQL.

Not because we want it to be, but because Oracle has left us no choice.