4 ms·
Agreed - Percona Community Edition is pretty dang good.
by thejosh 14y ago
Agreed - Percona Community Edition is pretty dang good.
- jacques_chester 14y agoI poked around a bit before picking it. The monitoring is what sold me -- I don't do anything like enough traffic for the performance stuff to affect me. I looked at MariaDB, Percona and Drizzle. MariaDB is very close to stock MySQL, Percona is stock + lots of performance patches and monitoring. Drizzle was still in the middle of proving Fredrick Brooks right about second systems.
- jmspring 14y agoUnderstanding the drop-in aspect, I'm curious if you compared those same three against Postgres? I'm contemplating which DB to move to for a project. I know Mysql and Postgres pretty well.
- jacques_chester 14y agoI greatly prefer PostgreSQL. But it's for a Wordpress installation.
- whalesalad 14y agoI believe the next version of WP is supposed to move away from a MySQL requirement by way of finishing their database abstraction. If I wasn't half asleep, on cold meds, and typing from my phone I'd validate that and share a link. I'm pretty sure it's in their near future though. Something in regards to PDO is ringing a bell.
- jacques_chester 14y agoPlugins and themes assume MySQL. Not all of them go through the Wordpress interface to the database.
- thejosh 14y agoThey aren't plugins/themes you want to be using than...
- LeonidasXIV 14y agoThe same could be said about blog engines that rely exclusively on using MySQL.
- whalesalad 14y agoPostgres is hard to beat right now in terms of the community behind it and the rate of innovation. Everyone is using it in exciting new ways. Hstore is awesome. Postgis is awesome. Async indexing. Heroku Postgres. The list goes on and on. That being said, most of the big projects that I've worked on in my lifetime were on MySQL and it fared very well. Mariadb and Percona are both solid. At some point all of the MySQL variants are still MySQL though... Which means a lot of its inherent flaws are still there. At the end of the day it's not tremendously hard to switch from one to the other. See the recent posts from the Lanyrd dev team on migrating to Postgres.
- bratsche 14y agoI've only used MySQL in jobs, but for a personal project I recently changed from MySQL to Postgres just as a learning exercise and because everyone has such great things to say about it. I'm very excited about learning more.
- jmspring 14y agoI've often used both for different projects, depending on the wrappers provided. Most of the PHP CMS world was all about MySQL first and foremost, which isn't a bad thing. But, if you ran into a MySQL limitation, you were pretty much stuck with trying to work around it -- see some of the notes about WP. Moving to an ORM layer or a level (or two) up from direct DB calls can result in more generic SQL and potentially a performance impact.
- jacques_chester 14y agoMy view is that these days, DBMS vendor lockin just isn't a problem if you're using an open source database. So you might as well take full advantage of the features that are available.
- taligent 14y agoArchitecture is a big part of it IMHO. Products exist like Oracle MySQL cluster or Percona XtraDB which allow you to do scale horizontally e.g. multi-master and have good support as you do grow. Nothing really exists for PostgreSQL on either front. But if you are planning to scale vertically then PostgreSQL seems the clear winner.
- jacques_chester 14y agoMySQL didn't become popular because it had multi-master. It got multi-master after it was popular.
- taligent 14y agoWho ever said it did ? I am just saying is it important to consider when evaluating databases.
- jacques_chester 14y agoSorry, for some reason I was under the impression that you were saying MySQL was popular because of its replication/HA features. On second reading, I'm wrong.