3 ms·

I think especially in the context of a "boring" web stack, MySQL is the clear winner. Postgres has lots of shiny features on the SQL side, but MySQL's storage

I think especially in the context of a "boring" web stack, MySQL is the clear winner. Postgres has lots of shiny features on the SQL side, but MySQL's storage and especially replication has always been more reliable for me. I've seen a couple failed MySQL -> Postgres migrations because it's the shiny thing people chase, but the operational reality is that MySQL is still better.

ThrustVectoring 10y ago
As an application developer, I remember wrestling with some really annoying stuff on the application side to deal with MySQL. IIRC, it was something like the default ORM for a python-based framework requiring a reflection API that Postgres and SQLite have and MySQL doesn't. This and other war stories probably generalizes to many other application developers preferring Postgres, but there's a ton of people using MySQL, so that probably means that it solves a bunch of the problems that the wizards in operations have. That's why I listed both. I'd use and recommend Postgres as a default in a heartbeat based off personal experience, but I wouldn't have personal experience with MySQL's strengths and people use and recommend it as well.