MariaDB is the natural replacement for MySQL. Why? Because it is the organic continuation of the MySQL that conquered the Internet. MySQL 8.0 is a fork of that foundation, while MariaDB stayed on track.
IGnatius T Foobar !: MySQL is dead. Long live MariaDB.
We’ve seen this many times before. For example, when OpenOffice went to die, LibreOffice took its mantle. XLibre has taken the mantle of Xorg. Likewise, MariaDB has taken the mantle of MySQL. These things happen. Let it happen.
⬆︎38 ⬇︎3
Z-: MySQL and MariaDB aren’t compatible.
⬆︎2 ⬇︎19
BasicReality: What we don’t need is another fork of a project. Oracle is a terrible company, when it acquired MySQL everyone should have known it would eventually be the end. MariaDB handled that, go support them, don’t repeat efforts for something else again.
⬆︎65 ⬇︎4
Let me highlight the article comments – including the current votes. The section headers are mine; the comments themselves are quoted verbatim.
No need for another fork. MariaDB does the job.
Why then are we thinking it needs another fork? As you said, support MariaDB. That is what it is meant for. It’s meant to be the replacement!!!!
⬆︎51 ⬇︎3
MariaDB is by design THE replacement for MySQL
wolfetone: This is really what I don’t get.
Nate Amsden: maybe not 100% compatible(there are issues with that even between versions of mysql or mariadb), but my org moved everything from mysql(5.x, technically percona I believe) to mariadb(10.x) a decade ago and there was zero issues with any applications(both in house developed and external). I think we even replicated directly from mysql to mariadb at the time(but I could be remembering that part incorrectly it was a while ago).
Often, comments to an article are more telling than the article itself. This is one such case. The article speculates about new forks of MySQL – and the comments do an excellent job of explaining why MariaDB is exactly the fork needed, with all the necessary components.
MariaDB is compatible with MySQL
We have been here before when Oracle bought MySQL and Monty spun out MariaDB as a direct replacement for MySQL. Every Linux distrobution I can think of, when you install or want to install MySQL you get MariaDB. Because MariaDB is the replacement.
There were some issues when it came to using galera clustering but that was galera specific, didn’t apply to standalone instances, actually ran into another such issue just yesterday with an old app, trying to upgrade to a newer version of it on a clustered galera mariadb, failed to apply schema updates because the new table being created lacked a primary key so the cluster rejected it, temporarily moved the app to a standalone instance to get around that and can fix the primary key(s) later and import back to the cluster(tiny DB)
⬆︎19 ⬇︎0
As the Chairman of the MariaDB Foundation, and someone having joined MySQL AB’s management team in 2001, that is my response to the article As Oracle loses interest in MySQL, devs mull future options in The Register. It already has many comments, though mine has not yet gone live. A good 8 h ago, I was assured the post will be updated “soon” and requested to be patient. Perhaps I should be more patient.
Z-: MariaDB isn’t compatible with MySQL and doesn’t try to be.
⬆︎1 ⬇︎15
MariaDB has taken the mantle of MySQL
That said, the MySQL fork is soft: Compatibility remains remarkable and migration back to the mothership is smooth.
