Re: > Subject: Re: Detailed explanation why uber move from postgress to mysql

From: Powell, Mark <>
Date: Thu, 22 Dec 2016 15:33:41 +0000
Message-ID: <AT5PR84MB019386FE6256C89F1819C9CBCC920_at_AT5PR84MB0193.NAMPRD84.PROD.OUTLOOK.COM>

Dave, try again,

Atomicity, Consistency, Isolation, Durability = ACID

LOL - Mark -

From: <> on behalf of <> Sent: Thursday, December 22, 2016 2:58:40 AM To:
Subject: Re: > Subject: Re: Detailed explanation why uber move from postgress to mysql

On 16-12-21 11:05 PM, FreeLists Mailing List Manager wrote:
> Date: Wed, 21 Dec 2016 20:39:37 +0100 (CET)
> From: Daniel Westermann <>
> 2TB is in no way a limit

I would agree, it's just I don't jump to recommend it at that level. A database that size usually has other ...... complications?

> From: "Juan Carlos Reyes Pacheco" <>
> Basically is what had been said previosly postgress is good for small business database not for bigger,
>personally I still found postgress better than mysql, based on what I read :).

I've worked with both.
I can make mysql outperform any database, including Oracle, on any dataset under 2TB. What I cannot do is make it ACID compliant and perform like that. mysql was originally designed for throughput, all transaction stuff is an addon and it shows.

The reason Uber went to mysql is they don't care. Throughput is most important to them. They can afford to deal with the inconsistencies because of the mass of data they have. After all most of their money comes from selling your trip data. And I'll bet you their payment processing system is not on mysql.

Oh no I used an abbreviation, I never even went to geek schoool. Calm down, I can do this:

A - Atomic?
C - Complete I know this one :)
I - Independant Know this one 2
D -

This is why I'm on the internet someone knows what the D is for, :)


Dave Morgan
Senior Consultant, 1001111 Alberta Limited
403 399 2442

Received on Thu Dec 22 2016 - 16:33:41 CET

Original text of this message