Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.

Why Uber switched from Postgres to MySQL

posted by n1 on Thursday July 28 2016, @06:30AM   Printer-friendly
from the they-forgot-about-mssql dept.

[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

Original Submission

 
This discussion has been archived. No new comments can be posted.
Why Uber switched from Postgres to MySQL | Log In/Create an Account | Top | 34 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 5, Touché) by wonkey_monkey on Thursday July 28 2016, @07:44AM

    by wonkey_monkey (279) on Thursday July 28 2016, @07:44AM (#381095) Homepage

    MySQL has been the darling of lampers for, like, ever.

    Well... yeah. Kinda by definition.

    --
    systemd is Roko's Basilisk
    Starting Score:    1  point
    Moderation   +3  
       Touché=3, Total=3
    Extra 'Touché' Modifier   0  
    Karma-Bonus Modifier   +1  
    Total Score:   5