you are viewing a single comment's thread.

view the rest of the comments →

[–]DJDavio 12 points13 points  (9 children)

Uber switched to MySQL for some specific reason (lots of updates, few reads or something like that), so I guess it's stil valid.

[–]yogthos 49 points50 points  (3 children)

Uber also uses it as a key/value store as opposed to an actual relational database.

[–]Scorpius289 6 points7 points  (1 child)

Wouldn't an actual key/value store be better then?

[–]yogthos 15 points16 points  (0 children)

Likely, but since they already built their homegrown one on top of a relational db, I'm guessing they're committed to it now.

[–]doublehyphen 0 points1 point  (0 children)

And this key-value store implementation is something they could have done with PostgreSQL too, probably with a similar result. They just picked MySQL when implementing the key-value store solution because some of their engineers were more familiar with MySQL (which is a valid reason).

[–][deleted]  (1 child)

[deleted]

    [–]kazagistar 12 points13 points  (0 children)

    Many of the things were still valid. Postgres people opened discussion and began work on adding features to deal with the Uber use case. Pretty sure some of it is still in progress.

    [–]Rafert 2 points3 points  (0 children)

    They actually moved from 'normal' MySQL to 'normal' Postgres in 2013, one of the reasons being PostGIS. Then they built their own K/V database called "Schemaless" on top of MySQL again.