News for hackers. Stuff that matters.
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.

* https://github.com/facebook/mysql-5.6/tree/webscalesql-5.6.2...

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?

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.