MindOpener
1000 record / sec is nothing for both Mysql or Postgres. Latency and response time will start to change depending on the size of the row you’re inserting, how many indexing you have, do you have text, json.
Mysql (using load data infile) can load 100,000+ rows per second.
It all depends what your writes need are : (referential integrity, critical transactions). If you need to store data for Audit purpose Mysql and Postgres might not be the best solution. I would look into MemSQL which was built for fast ingestion and analytical queries.
I’m sure Uber did their homework. You don’t switch from one DB to another just because one guy prefers Postgres.
Research and test (benchmarks) is a must. Lots of biased benchmarks out there that probably don’t match your workload and table structure.