Nothing hugely complicated. Production Magento, Drupal and WordPress - we managed to outsource the WordPress, so now it's mainly now Magento, and that's much mo

Nothing hugely complicated. Production Magento, Drupal and WordPress - we managed to outsource the WordPress, so now it's mainly now Magento, and that's much more horrible in itself than MySQL - one in-house tool that used to use it, some MediaWiki, and one really badly-behaved in-house tool that picked MySQL without asking us first. Mostly we were bitten by long-running MySQL sillinesses: * its strange idea of UTF-8 (we call the MySQL version WTF-8 - see http://geoff.greer.fm/2012/08/12/character-encoding-bugs-are-%F0%9D%92%9Cwesome/ http://geoff.greer.fm/2012/08/12/character-encoding-bugs-are... ) * InnoDB's galloping disk consumption * the Debian/Ubuntu package's default stupid behaviour of putting all the InnoDB databases into a single file ibdata1 (I hope this is a Debianism and not something that's default in upstream) * ibdata1 never shrinking ever (bug #1341, open since 2003) * binary replication issues (e.g. bug #68892, which is fixed but that doesn't help older or distro versions) * several others I've mercifully obliterated the braincells that were holding them. But all of these were long-known issues that will never be fixed for one reason or another (backward compatibility with past mistakes, or they just can't be bothered). Here's a good crib: http://grimoire.ca/mysql/choose-something-else http://grimoire.ca/mysql/choose-something-else tl;dr MySQL: the Comic Sans of databases. Except Comic Sans has use cases.