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

• Limitations (Score: 3, Funny) by Anonymous Coward on Thursday July 28 2016, @07:25AM

  by Anonymous Coward on Thursday July 28 2016, @07:25AM (#381091)

  [...] 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
  Inability to screw over drivers
  Excessive accuracy on actual drive times
  No way to overvalue tips to drivers
  Inability to determine sex-offender status of driver, or passengers
  Quantum instability on stock price

  Fixed some of that for you, bro!

  Starting Score:	0		points
  Moderation		+3
  Informative=1, Funny=2, Total=3
  Extra 'Funny' Modifier		0
  Total Score:		3