Why Uber Engineering Switched from Postgres to MySQL

Re:Why Uber Engineering Switched from Postgres to MySQL by _Codemonkeyism on Tuesday July 26, 2016 @02:24PM (#12167716)

"1B+ rows in it with mysql?"

Been there, really no fun.

[ Parent | on HN ]

Re:Why Uber Engineering Switched from Postgres to MySQL by midom on Tuesday July 26, 2016 @02:37PM (#12167827)

As long as you can shard (across multiple instances, or even within same instance, to avoid B-Tree latching), 1B+ rows within MySQL is piece of cake.

Also, MySQL* is getting LSM-Tree support lately, which makes high performance data ingestion combined with OLTP workload quite feasible.

[ Parent | on HN ]

Re:Why Uber Engineering Switched from Postgres to MySQL by _Codemonkeyism on Tuesday July 26, 2016 @11:17PM (#12170271)

"I wonder how Uber adds an index to a table that already has 1B+ rows in it with mysql?"

"As long as you can shard "

Not sure how sharding helps with 1B+ tables when adding indices, care to share?

[ Parent | on HN ]

Re:Why Uber Engineering Switched from Postgres to MySQL by Swannie on Wednesday July 27, 2016 @08:06PM (#12177465)

This is: "Split the index in your application code."

And then do your joins, in your application code.

[ Parent | on HN ]

Re:Why Uber Engineering Switched from Postgres to MySQL by fasteo on Tuesday July 26, 2016 @03:02PM (#12168016)

Percona to the rescue [1]. Works flawlessly, at least in our case.

[ Parent | on HN ]

Re:Why Uber Engineering Switched from Postgres to MySQL by barrkel on Tuesday July 26, 2016 @05:49PM (#12168974)

Am there right now, it's not really a problem - you just have to plan your schema changes and use Percona OST.

[ Parent | on HN ]

Re:Why Uber Engineering Switched from Postgres to MySQL by maximegarcia on Tuesday July 26, 2016 @04:27PM (#12168522)

Saved my life a few time :)

[ Parent | on HN ]

Re:Why Uber Engineering Switched from Postgres to MySQL by _Codemonkeyism on Tuesday July 26, 2016 @11:19PM (#12170284)

Thanks!

[ Parent | on HN ]

Re:Why Uber Engineering Switched from Postgres to MySQL by Groxx on Saturday August 06, 2016 @07:45PM (#12240407)

Also been there. Percona Toolkit works fine (though it's not load-aware enough, so we changed the backfill logic).

Plus, in 5.7, there are a fair number of online-DDL changes, and adding indexes is (usually) one of them.

[ Parent | on HN ]