3 ms·
I like MariaDB improvements over MySQL (and the technical documentation of the query's optimizations), but I'm a bit lost regarding WebScaleSQL's [1] choice to
by maximegarcia 13y ago
I like MariaDB improvements over MySQL (and the technical documentation of the query's optimizations), but I'm a bit lost regarding WebScaleSQL's [1] choice to tracks MySQL. I don't know what to think... Google, Facebook, Twitter & co have immediate production needs, so are they simply in "wait and see" mode toward MariaDB ? Or is there something deeper ?
[1] http://webscalesql.org/ http://webscalesql.org/
- meritt 13y agoNo clue. I'd personally stick with Maria or Percona if you're looking for serious improvements to MySQL by extremely talented engineers.
- opendais 13y agohttp://www.theregister.co.uk/2013/09/12/google_mariadb_mysql_migration/ http://www.theregister.co.uk/2013/09/12/google_mariadb_mysql... My guess is there isn't an enforced MySQL version across all of Google. "We asked Google for more information, and the company sent us a statement which said: "Google's MySQL team is in the process of moving internal users of MySQL at Google from MySQL 5.1 to MariaDB 10.0. Google's MySQL team and the SkySQL MariaDB team are looking forward to working together to advance the reliability and feature set of MariaDB."
- cwyers 13y agoFrom the FAQ on that page: "Q: Why didn't you base this on MariaDB, Percona Server, Drizzle, etc.... A: We reached a consensus that MySQL-5.6 was the right choice for this, as it has the production-ready features we need to operate at scale, and the features planned for MySQL-5.7 seem like a fitting path forward for us. We will continue to revisit this decision as the ecosystem evolves." MariaDB 10 just hit after the launch, much less conception, of Webscale, and still doesn't have all of the features from MySQL 5.6 in it.
- tszming 13y agoBecause companies like Facebook are more interested in stuffs like InnoDB improvements in MySQL 5.6/5.7 than those nosql/sharding features which they already have their own workarounds.