SoylentNews

Why Uber switched from Postgres to MySQL

posted by n1 on Thursday July 28 2016, @06:30AM   
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

• Re:On the other hand (Score: 3, Touché) by Common Joe on Thursday July 28 2016, @03:14PM

  by Common Joe (33) <common.joe.0101NO@SPAMgmail.com> on Thursday July 28 2016, @03:14PM (#381220) Journal

  Sounds like you're the AC who was "uncivil" to me. I'm glad you're reading my followup stuff.

  What I'm most happy about is you had a good and informative reply. (Thank you.) Yeah, you were a bit uncivil, but you're an AC, this is the Internet, and I tried to pay attention more to learning from your response.

  Parent

  Starting Score:	1		point
  Moderation		+1
  Touché=1, Total=1
  Extra 'Touché' Modifier		0
  Karma-Bonus Modifier		+1
  Total Score:		3