Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If you know MariaDB, what's your opinion about migrate applications to use MariaDB instead of MySQL?

What we gain and what we lost with this change?

Is it really unnecessary to change the application in any situation?

Any tip to assure the application run smoothly on MariaDB?

share|improve this question

closed as primarily opinion-based by Doval, Tulains Córdova, GlenH7, Bart van Ingen Schenau, gnat Aug 10 '14 at 18:07

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 6 down vote accepted

MySQL still has the advantage of being bigger than the forks and clones. Bigger in the sense of number of users and expertise that is available. It has taken a long time for MySQL to become a 'safe' choice to use for companies. That reputation wont be lost overnight, nor will it be gained by MariaDB soon either. In a commercial environment it matters and it will be hard to introduce MariaDB in a lot of places.

You mention migrating in your question. Migrating is hard, particularly for lower level 'stuff' and especially data storage. I wouldn't recommend it unless there was a specific benefit from doing it.

share|improve this answer

I really don't see the point. MySQL is a mess anyway, and a fork of it is going to inherit all its quirks and gitches. If you want to move off of MySQL, why not just switch to Firebird, a free and open source DB that doesn't feel like a toy whenever you try to use it?

share|improve this answer
Postgresql is also a viable alternative. – Robert Harvey Sep 24 '10 at 1:44
+1 indeed @Robert Harvey, you may know, but for benefit of those that don't, major web CMS drupal supports this as well as MySQL – therobyouknow Dec 18 '10 at 10:18

The whole thing is moot.
Percona Server does what MySQL does (100% compatible), but does it right, fast and while using less resources.
In many ways it's like Maria, only taking it one more step.

After doing extensive testing in our test environment to ensure it's as compatible and easily interchangeable as it says on the tin, I was able to swap out our production MySQL for Percona in about 2 minutes. I timed it in such a way that I was able to do it during production hours without noticeable downtime.

So yeah, if you're going to swap out MySQL, swap it out for Percona.

share|improve this answer

far as i known MariaDb isn't productive quality already. But i think that she is (yes, is a woman) the future. Software is more the people involve in it that the branding name

share|improve this answer
RE: "she is (yes, is a woman)" Not quite. MariaDB is created by the same guy who created the original MySQL, Monty Widenius. He named it after his daughter. – user36644 Sep 14 '11 at 0:38
FWIW, MySQL was also named after his daughter - My (sounds like Mui). So My is Maria's sister - literally. – slebetman Aug 11 '14 at 4:19
I downvoted this answer because the claim "MariaDb ist the future" is not backed up by anything. – Philipp Aug 11 '14 at 14:51

Not the answer you're looking for? Browse other questions tagged or ask your own question.