You gave one example of each. That's a pretty painful definition of the word 'every'. On performance: Every database will have some areas where it performs bet

You gave one example of each. That's a pretty painful definition of the word 'every'. On performance: Every database will have some areas where it performs better than others - Uber just happened to hit a case that MySQL is well optimised for. On data loss: MySQL's binlog replication is hardly a 'just works' solution. It's definitely got a lot better over time (particularly in 5.7), but it's not like a replica falling behind is some incredibly unusual event. Go back a fair while and it was really broken - much more so than Postgres' solution has ever been. It's fair to say it's more mature right now, and one reason to prefer MySQL for replication is that there's certainly more help out there for it.