Why Uber Engineering Switched from Postgres to MySQL

Content is AI-assisted and may contain inaccuracies.

Uber Engineering's article revisits the database decision behind its move away from Postgres. Uber's early stack was a monolithic Python backend with Postgres for persistence; as the architecture shifted to microservices, many of those workloads moved to Schemaless, a database sharding layer built on top of MySQL.

The post documents the limitations the team ran into with Postgres at that scale and explains why Schemaless and later backend services were built on MySQL instead. The writeup is a first-hand account of migrating a large service off a relational database.

Sources

Tags