Why Uber Engineering Switched from Postgres to MySQL
1–10 of 306 posts
Re: Why Uber Engineering Switched from Postgres to MySQL
#2This was a great overview and write-up.
Anyone know why they are using MySQL over MariaDB[1]?
Re: Why Uber Engineering Switched from Postgres to MySQL
#3this reads like a laundry list of buzzwords that were designed to justify not throwing any effort into postgresql and just going with a new shiny toy (not mysql. yes. i know it's been around for a while).
it happens everywhere.
Re: Why Uber Engineering Switched from Postgres to MySQL
#4I've heard from technical leaders at multiple now well established unicorns how they'd never use postgres or switched from postgres simply because MySQL has a lot more tooling built it and many more people are exposed to its shortcomings at "web scale" so that it's very well known where and when things will break.
Disclaimer, I'm a hardcore Postgres user myself, but I also keep tabs on the other tools.
Re: Why Uber Engineering Switched from Postgres to MySQL
#5Facebook maintains it's own fork [0] of MySQL. A couple of interesting talks are also available: MySQL at Facebook, Current and Future [1] and Massively Distributed Backup at Facebook Scale [2].
[0] https://github.com/facebook/mysql-5.6
Re: Why Uber Engineering Switched from Postgres to MySQL
#6this reads like a laundry list of buzzwords that were designed to justify not throwing any effort into postgresql and just going with a new shiny toy (not mysql. yes. i know it's been around for a while). it happens everywhere.
From the post:
> [...] This design difference means that the MySQL replication binary log is significantly more compact than the PostgreSQL WAL stream.
Doesn't sound like what you described at all.
Re: Why Uber Engineering Switched from Postgres to MySQL
#7this reads like a laundry list of buzzwords that were designed to justify not throwing any effort into postgresql and just going with a new shiny toy (not mysql. yes. i know it's been around for a while). it happens everywhere.
Yes, MySQL, the shiniest of new toys...
Re: Why Uber Engineering Switched from Postgres to MySQL
#8this reads like a laundry list of buzzwords that were designed to justify not throwing any effort into postgresql and just going with a new shiny toy (not mysql. yes. i know it's been around for a while). it happens everywhere.
now sure MySQL qualifies as "new" or "shiny" or "toy"
Re: Why Uber Engineering Switched from Postgres to MySQL
#9Well, this is heresy. Does that mean we are now officially boycotting Uber?
Joke asides, one thing I've been trying to figure out for awhile is the limitation at which certain components/ systems broke down. Basically, something along the line of "given X records, this operations would take Y time, or would cause Z A B C problems". I've actually got developers friends asking me how fast a simple "SELECT * FROM X WHERE index=?" would take on a million row table, since they were surprised that some NoSQL DB could do a query on hundred million rows in a few seconds.
I guess that's part of why you only learned how to scale after having done it once.
Re: Why Uber Engineering Switched from Postgres to MySQL
#10[deleted]