I also dumped MySQL and started using and recommending MariaDB in production since i've seen it resolve a lot of my hard fought battles with super complex nested joins and index overloads. Queries that took 4.5s went to 450ms just by dropping in this beauty. From then on I was on the bandwagon. Slow Wordpress site with a ton of plugins that tries to solve everything? Now it can do it within a timeframe thats acceptable. Ok your bottlenecks will still be there somewhat.. abeit less apparent. But it just is faster and scales way more predictable imo with hardware adapted configs.
It's pretty similar to the Hudson/Jenkins situation (also something acquired by Oracle). Kind of sad when the original author has to fork his own project to keep evolving it, but I'm glad they're apparently able to take a considerable amount of users with them.
We also switched to MariaDB in production a while ago. Was absolutely seamless.
Kind of sad when the original author has to fork his own project But pretty awesome that Free Software gives him (or her) the right to do so. It used to be you abandoned your code when acquired.
For Jenkins - they took almost all the users. I doubt we'll hear much about Hudson in 5 years time, unless something major happens. I think only Oracle, Sonatype and a handful of other companies are using Hudson these days. All the companies I know have migrated to Jenkins.
One might think that but it has surprisingly not been true.
Oracle, already the owner of InnoDB, now owning the entirety of mysql has been able to stop fighting with Sun and push out awesome features at a high rate. Just to name a few since Oracle took over:
* Big performance improvements for multi-core.
* Performance Schema
* Full-text engine for InnoDB
* Thread pools
* Improved support for SSD
* Online schema updates
MariaDB forked at 5.5 and is going to be missing lots of really nice features. They can back port some of it but they aren't going to be able to keep up very well. They have their own implementation of some of these features which, given their small user base, I do not trust as much as the versions implemented in MySQL proper.
Also given that MariaDB was forced to merge with SkySQL to survive I just don't see a bright future for MariaDB as long as Oracle continues to improve MySQL like it has been.
Oracle didn't buy the product. They bought the name and the product was a nice extra. Likewise Oracle didn't really buy Java; they bought Sun and Java just happened to be a nice extra.
I've heard people say this was like what Cisco tried to do with Linksys by trying to get into consumer and SMB. Plus we know from Cisco what happens when you buy a brand and let it stagnate.
Buying MySQL for Oracle, I think, wasn't really a matter of creating a new foothold in the hobby/SMB market or the like. Bringing it under their name was about adding value to their own brand. "Look, we cater to the 'small' guys too!" (And that's however arbitrarily people define 'small' since Adwords clearly doesn't fit the label.) If it was somehow about gaining a foothold, I think that was secondary. And maybe it was their way of somehow muscling in on Postgres in that aspect.
Of course people will only continue to use a product if you show it some love. Freshly harvested fruit has a limited shelf life after all.
Percona are part of the MariaDB foundation, though so far they still seem to be based off of Oracle's MySQL sources.
Red Hat's announcement wasn't much of a surprise (Fedora had adopted MariaDB some time ago, as has most of the rest of the known universe). A lot of enterprises rely on Percona for support and consulting, however, and should they make a switch, that's likely lights-out for MySQL. Though there's a low probability Oracle would consider transferring the name to a community foundation outside its control (the codebase really doesn't matter as it's GPLd) and the name could continue forward.
It's a pretty powerful message of how branding isn't the end-all in Free Software.
Basically we have chosen Percona to by our MySQL 'base'. Essentially even if they switch to MariaDB as the core I can expect a seamless transition and support to back it up if needed. Essentially if the crap ever truly hits the fan with Percona solutions they can charge us for some hours. If the same happens with MariaDB it's pretty much 'me'.
I also looked at percorna before even knowing about MariaDB. I ended up picking MariaDB because it solved more of the issues that I currently had in a codebase that I simply did not get the resources for to get refactored in a way. Also in comparison to Pecorna, you also get Aria, which aims to be a transactional/non-transactional replacement for MyISAM. Can't wait for that moment :)
In somewhat related news, I wonder how much longer MariaDB will be a "free for all" given Monty's view on open source and open development seems to have changed:
They've announced [1] that RHEL 7 will be based on Fedora 18. Based on the package updates list for mongodb [2], it looks like it will using MongoDB version around 2.2.4. The source should be available via Fedora's normal repos.
Yes existing MySQL tooling works with MariaDB. The wire protocol is still the same so existing MySQL drivers work to connect to MariaDB as well.
The reverse situation is also useful. The MariaDB client drivers can connect to both MariaDB and MySQL instances yet are licensed LGPL (vs GPL for the MySQL client drivers) which is great for closed source commercial products (and general license compatibility).
We use it in the in house deployed version of our product (database client in your browser[1]) and will be switching the cloud hosted version over to it soon as well. No issues with it so far.
I use MariaDB in production. It was totally trivial to drop it in as a MySQL replacement and usually gets slightly better performance. Not to mention not relying on Oracle who one can imagine might not want to give MySQL as much love as it needs given their other database. So I can see why Redhat would want to do that.
As for the name, MySQL was named after Monty's daughter My. MariaDB was named after another daughter Maria (http://en.wikipedia.org/wiki/Michael_Widenius). I think its sort of sweet. Maybe someone has a kid called Postgre? ;-)
yeah, they should've chosen something more pronounceable, like "PostgreSQL" </sarcasm> ...seriously now, the only db with a "decent" name (easy to pronounce, nice sounding and actually meaningful) is Oracle, and maybe this was a reason for their success.
It is not that MariaDB is any better, it is that Oracle is much bigger.)
Edit: It is all about InnoDB engine, which is now developed and fixed by Oracle. Others, notably Percona, have its own set of patches which adds some features to what Oracle releases, while MariaDB is mostly re-branding.
MariaDB right now has working Multi-Source replication and GTID failover in the MariaDB 10.0.3+ alphas.
They are also working on a new table discovery engine, which will bring Transactional DDL to MariaDB, this to me makes MariaDB far more superior to MySQL. They are innovating, and they are open about it.
https://mariadb.atlassian.net/browse/MDEV-3808
Oracle have only innovated on the niggles of Mysql, like the unencrypted ~/.my.cnf files to appease their "Enterprise" customers.
[+] [-] easy_rider|12 years ago|reply
[+] [-] rz2k|12 years ago|reply
[+] [-] fhd2|12 years ago|reply
We also switched to MariaDB in production a while ago. Was absolutely seamless.
[+] [-] dredmorbius|12 years ago|reply
[+] [-] oblio|12 years ago|reply
[+] [-] JimmaDaRustla|12 years ago|reply
Not sure how the original developers can create a fork of a product they sold for 1 billion? Oh well, better in their hands than Oracle's.
[+] [-] leef|12 years ago|reply
One might think that but it has surprisingly not been true.
Oracle, already the owner of InnoDB, now owning the entirety of mysql has been able to stop fighting with Sun and push out awesome features at a high rate. Just to name a few since Oracle took over:
* Big performance improvements for multi-core.
* Performance Schema
* Full-text engine for InnoDB
* Thread pools
* Improved support for SSD
* Online schema updates
MariaDB forked at 5.5 and is going to be missing lots of really nice features. They can back port some of it but they aren't going to be able to keep up very well. They have their own implementation of some of these features which, given their small user base, I do not trust as much as the versions implemented in MySQL proper.
Also given that MariaDB was forced to merge with SkySQL to survive I just don't see a bright future for MariaDB as long as Oracle continues to improve MySQL like it has been.
[+] [-] glurgh|12 years ago|reply
Product was GPL licensed. For many years before Oracle bought it.
[+] [-] eksith|12 years ago|reply
I've heard people say this was like what Cisco tried to do with Linksys by trying to get into consumer and SMB. Plus we know from Cisco what happens when you buy a brand and let it stagnate.
Buying MySQL for Oracle, I think, wasn't really a matter of creating a new foothold in the hobby/SMB market or the like. Bringing it under their name was about adding value to their own brand. "Look, we cater to the 'small' guys too!" (And that's however arbitrarily people define 'small' since Adwords clearly doesn't fit the label.) If it was somehow about gaining a foothold, I think that was secondary. And maybe it was their way of somehow muscling in on Postgres in that aspect.
Of course people will only continue to use a product if you show it some love. Freshly harvested fruit has a limited shelf life after all.
[+] [-] Aqueous|12 years ago|reply
[+] [-] lotsofcows|12 years ago|reply
[+] [-] dredmorbius|12 years ago|reply
Red Hat's announcement wasn't much of a surprise (Fedora had adopted MariaDB some time ago, as has most of the rest of the known universe). A lot of enterprises rely on Percona for support and consulting, however, and should they make a switch, that's likely lights-out for MySQL. Though there's a low probability Oracle would consider transferring the name to a community foundation outside its control (the codebase really doesn't matter as it's GPLd) and the name could continue forward.
It's a pretty powerful message of how branding isn't the end-all in Free Software.
[+] [-] druiid|12 years ago|reply
[+] [-] easy_rider|12 years ago|reply
[+] [-] binarycrusader|12 years ago|reply
Fluffy summary:
http://readwrite.com/2013/05/31/mysql-co-founder-wants-you-t...
Original interview:
http://www.zdnet.com/open-source-its-true-cost-and-where-its...
[+] [-] JeremyMorgan|12 years ago|reply
[+] [-] sturadnidge|12 years ago|reply
[+] [-] csears|12 years ago|reply
[1]: http://www.h-online.com/open/features/Red-Hat-s-RHEL-7-roadm... [2]: https://admin.fedoraproject.org/updates/mongodb
[+] [-] josephlord|12 years ago|reply
I'm sure there are many that use the distribution default but I wonder if anyone is actively choosing MySQL still.
[+] [-] Jagat|12 years ago|reply
[+] [-] chiph|12 years ago|reply
[+] [-] sehrope|12 years ago|reply
The reverse situation is also useful. The MariaDB client drivers can connect to both MariaDB and MySQL instances yet are licensed LGPL (vs GPL for the MySQL client drivers) which is great for closed source commercial products (and general license compatibility).
We use it in the in house deployed version of our product (database client in your browser[1]) and will be switching the cloud hosted version over to it soon as well. No issues with it so far.
[1]: http://www.jackdb.com/
[+] [-] endijs|12 years ago|reply
[+] [-] bunwich|12 years ago|reply
[+] [-] tyree732|12 years ago|reply
[+] [-] ciderpunx|12 years ago|reply
As for the name, MySQL was named after Monty's daughter My. MariaDB was named after another daughter Maria (http://en.wikipedia.org/wiki/Michael_Widenius). I think its sort of sweet. Maybe someone has a kid called Postgre? ;-)
[+] [-] dorfsmay|12 years ago|reply
[+] [-] selectnull|12 years ago|reply
[+] [-] riffraff|12 years ago|reply
[+] [-] tzaman|12 years ago|reply
[+] [-] nnq|12 years ago|reply
[+] [-] yen223|12 years ago|reply
[+] [-] clhodapp|12 years ago|reply
[+] [-] ollysb|12 years ago|reply
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] JimmaDaRustla|12 years ago|reply
[+] [-] shrikant|12 years ago|reply
[+] [-] dschiptsov|12 years ago|reply
Edit: It is all about InnoDB engine, which is now developed and fixed by Oracle. Others, notably Percona, have its own set of patches which adds some features to what Oracle releases, while MariaDB is mostly re-branding.
[+] [-] mathnode|12 years ago|reply
They are also working on a new table discovery engine, which will bring Transactional DDL to MariaDB, this to me makes MariaDB far more superior to MySQL. They are innovating, and they are open about it. https://mariadb.atlassian.net/browse/MDEV-3808
Oracle have only innovated on the niggles of Mysql, like the unencrypted ~/.my.cnf files to appease their "Enterprise" customers.