Wikipedia Adopts MariaDB
blog.wikimedia.org
blog.wikimedia.org
MariaDB looks likely to inherit a big slice, possibly even a majority, of MySQL's user base over time.
It's not just because MariaDB is as good as any of the "official" editions of MySQL offered by Oracle, but because it has only a single code base under a single Free license (as opposed to differently licensed "open source" and "enterprise" editions), because it has an active not-for-profit foundation looking out for the project and the community[1], and because many of the original contributors to MySQL, including founder Monty Widenius, are now working full-time on MariaDB.[2]
Say hello to the new MySQL -- MariaDB -- same as the old MySQL!
--
[1] https://mariadb.org/en/foundation/
[2] http://www.skysql.com/news-and-events/press-releases/skysql-...
"For our most common query type, 95th percentile times over an 8-hour period dropped from 56ms to 43ms and the average from 15.4ms to 12.7ms. 50th percentile times remained a bit better with the 5.1-facebook build over the sample period, 0.185ms vs. 0.194ms. Many query types were 4-15% faster with MariaDB 5.5.30 under production load, a few were 5% slower, and nothing appeared aberrant beyond those bounds."
The sooner we all can move on and keep from using MySQL, the better, and good riddance to it and the red horse it unfortunately rides in on.
It seems that MySQL development halted entirely at Sun.
I was concerned about Oracle's motives w.r.t MySQL but I can say they have come out with major new releases that improve MySQL in substantial ways. For instance, they've greatly improved the scalability of InnoDB on large SMP machines.
On the other hand, neither Sun nor Oracle have been really wanting to win with MySQL either and I think we could have seen more and different innovation in MySQL if it had been in other hands.
The Wikipedia win is big for MariaDB because it's a show of confidence that it works in demanding applications.
As a corollary, no one wants to be the guy that suggested MongoDB before it caused an outage.
What it isn't is a different program entirely, with a different protocol, syntax, scalability, consistency and community.
Here's how it works in most companies: MySQL goes down = something seriously bad happened. MariaDB went down = that database that Ted suggested sure is a piece of shit.
In the end it comes down to having data to support your position though. If MariaDB goes down, and you can't answer whether it would have happened the same in MySQL, then maybe you shouldn't be making database suggestions. If it wouldn't have happened to MySQL, well then people were right to be wary, weren't they?
However, there are of course also situations where, if you try to use MongoDB as a drop in replacement for a traditional database and then are surprised about data loss in exotic situations, for example, then you weren't really doing your job in the first place if the different goals never came up in your research of solutions.
May be the lots and lots of SPs are too much for MariaDB, but no, it is not a 100% replacement drop in.
I have tried.
In most cases Percona seems to be a win over both MySQL and MariaDB as it is just patch layer over MySQL with features and tweaks that real production users see and need. These features tend to end up in future MySQL releases like saving and restoring the buffer pool allowing mysql to warm start. I believe that feature made it in to MySQL 5.6 but was added to percona/mysql 5.1.
[1] http://blog.mariadb.org/mariadb-5-3-optimizer-benchmark/
http://dimitrik.free.fr/blog/archives/2013/02/mysql-performa...
Sure there are other fulltext solutions but to simply convert myisam to innodb, FTS on innodb with the same queries is rather helpful.
Having the same company own both the main engine (InnoDB) and the harness (MySQL) has been tremendously valuable.
I may be a bit ignorant, but what have they done with MySQL?
Perhaps "hate" is the wrong word, and it should be more "dislike", since Oracle are essentially the complete opposite of what Monty wants to encourage (e.g. Hacker Business Model, Open Source). My memory's a bit hazy, but from what I gathered, Oracle tried to stop MySQL in its early days by acquiring the INNODB Engine around 2005. After that, once Oracle acquired Sun and thus MySQL, Monty and many of the other original developers saw Oracle as being against the spirit of the original intention of MySQL, shifting away from the principles they wanted to encourage, particularly open source philosophies, and they wanted to make sure a version of MySQL would always stay free. From what I recall, he believed that Oracle were no longer fixing known bugs because they didn't know how, and they were also moving from "open source" to "open core", where new features were closed source.
I do appreciate Monty's efforts, but really, can we kiss and make up? And if oracle wants to monetize MySql, so what? The rest of us get a better database.
Also it should be noted that the InnoDB storage engine was developed outside of MySQL AB. InnoDB is a helluva lot better than MyISAM for most applications because of performance and support for transactions, consistency, etc. Without it I don't think that MySQL would be a good candidate for many applications, particularly given that Postgres has improved a lot. I.e. I'm not sure Monty should really get credit for everything about MySQL/MariaDB.
That said, I wouldn't put it beneath them...
Not that the takeover is feasible, as the other answers point out.