4 ms·
Looking at the specs for MariaDB, I can see why our last client dropped MySQL for the front end and went with it. The XtraDB engine, basically a fork of InnoDB
by eksith 14y ago
Looking at the specs for MariaDB, I can see why our last client dropped MySQL for the front end and went with it.
The XtraDB engine, basically a fork of InnoDB with patches, is actually very nice. We've had to do almost no modifications to the data structure when moving from InnoDB for some DBs (that we're not using Postgres for).
Fun fact: XtraDB is also the default in Percona http://www.percona.com http://www.percona.com (No, I don't work for them).
There are things you still need to carefully look into before migration if that's what you want to do. Minor things like naming is only part of it. Read. Read. Re-read the documentation :
https://mariadb.org/docs https://mariadb.org/docs
I've felt MairaDB is the direction MySQL should have gone after the 4.x branch. In many ways (though the technical aspects are totally different), this split is very similar to what happened with FreeBSD after the 4.x branch with the start of DragonFly. When in doubt, fork.
The beauty of Open Source.
- stock_toaster 14y agoXtraDB is not only the default in Percona, they originally wrote it (forked from InnoDB). http://www.mysqlperformanceblog.com/2008/12/16/announcing-percona-xtradb-storage-engine-a-drop-in-replacement-for-standard-innodb/ http://www.mysqlperformanceblog.com/2008/12/16/announcing-pe...
- olalonde 14y agoOut of curiosity, why do you need to use both Postgres and MySQL/MariaDB?
- eksith 14y agoOur clients usually have a lot already running on InnoDB so we always have similar setups (preferably identical except the same volume of data) to what they have on the side. Can't tell you how many problems we've caught that way and how much it simplifies things during deployment. If starting anew, it's Postgres. Our internal stuff is almost all running straight Postgres but a small part of our application stack is abstracted on top of it to provide document DB functionality.
- harichinnan 14y agoMysql cannot do parallel query. That's a single query won't spin off multiple threads and work in parallel. This makes it a bad solution for say aggregating over large data. Mysql can handle lots of threads(queries) in parallel making it an ideal solution for web. Postgres can do parallel query.
- HarrisonFisk 14y agoPostgreSQL doesn't do parallel query.
- EwanToo 14y agoMySQL can do parallel querying through some of the less common back-ends, like Infinidb, which are more suited to warehousing than OLTP like InnoDB/XtraDB. http://infinidb.org/component/content/article/53/158 http://infinidb.org/component/content/article/53/158