Poor replica MVCC support: Postgres does not have true replica MVCC support.This resulted in numerous incorrect timeline switches on replicas that were being undertaken. Issues with table corruption: During one of Uber’s routine master database promotion to increase database capacity, they encountered a Postgres 9.2 bug.The real problem with Postgres arises when replication is done between multiple data centers. Inefficient data replication: Postgres’ replication required higher bandwidth as compared to MySQL but Postgres replication may not be a problem within a single data center.Implementing a MVCC mechanism so that different connections have a transactional view of the data they work with.Providing capabilities for making schema changes.Providing efficient insert/update/delete capabilities.Inefficient architecture for writes: A relational database must perform certain key tasks that Postgres were not suited for Uber’s needs.Some of the key issues faced by Uber include: And we all agree to the fact that, downtime is the biggest enemy of a growing enterprise. One of the main limitations faced by Uber was its inability to optimize their upgrading process which resulted in downtime. Uber recently shared a blog detailing various issues they faced using Postgres and what prompted them to make the change to MySQL.
While enterprises are constantly checking and trying to find the right fit for their databases, it takes immense research and analysis to decide on THE one.Įach enterprise has their own requirements and it is imperative for the company to decide on the database that suits their needs. Recently, Uber also announced a major change – Changing their databases from Postgres to MySQL. Be it expansion to new countries or selling its China operations to Didi chuxing, Uber is growing exponentially and expanding into newer markets. Uber has been in the news for numerous reasons in the past few weeks.
0 kommentar(er)
