[redacted] Coward writes:
https://eng.uber.com/mysql-migration/
The early architecture of Uber consisted of a monolithic backend application written in Python that used Postgres for data persistence. Since that time, the architecture of Uber has changed significantly, to a model of microservices and new data platforms. Specifically, in many of the cases where we previously used Postgres, we now use Schemaless, a novel database sharding layer built on top of MySQL. In this article, we’ll explore some of the drawbacks we found with Postgres and explain the decision to build Schemaless and other backend services on top of MySQL.
[...] We encountered many Postgres limitations:
Inefficient architecture for writes
Inefficient data replication
Issues with table corruption
Poor replica MVCC support
Difficulty upgrading to newer releases
(Score: 3, Interesting) by frojack on Thursday July 28 2016, @07:30AM
The real news here is trendy Uber appers were using dinosaur tech in the first place. MySQL has been the darling of lampers for, like, ever.
Not so fast.
MySQL and Postgres have been dukeing it out for decades, and there was a loooong period of time when MySQL was just the upstart usurper, with a bunch of missing features and fragile releases. By the time Oracle stepped in it was pretty solid and had added most of the features it needed. Good thing too, because lots of devs ran away to MariaDB.
Probably when Uber hacked what ever they converted to start their system they should have started from scratch, but chances are they had something working when they started, or the only tool they had was a hammer so all the problems looked like nails.
No, you are mistaken. I've always had this sig.