Articles
Why Uber Engineering Switched from Postgres to MySQL
Evan Klitzke's 2016 post is still one of the most-cited, and most-argued-about, database migration writeups out there, walking through the specific Postgres limitations Uber hit at their scale, write amplification from secondary indexes, expensive replication, and a costly process-per-connection model, that pushed them toward a MySQL-backed sharding layer. I don't take it as gospel that Postgres is worse than MySQL in general (a lot has changed on both sides since 2016), but it's a genuinely useful case study in how workload-specific tradeoffs, not general benchmarks, should drive a database choice at scale. Worth reading the pushback pieces alongside it for the full picture.