Uber's Postgres to MySQL (2016)

Interesting look back to why Uber moved from Postgres to MySQL back in 2016

Note: this article is from 2016, but is still an interesting insight into why Uber decided to move from Postgres to Mysql.

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.