4 ms·
Can't agree with this post enough. I find their whole writeup to be terribly myopic. When they started their service, Postgres was almost certainly the right
by busterarm 10y ago
Can't agree with this post enough.
I find their whole writeup to be terribly myopic. When they started their service, Postgres was almost certainly the right choice for what they were building and their MySQL setup was not. Now Postgres is less effective for them.
These kind of tech switches are _inevitable_ if you're making the right choices for your organization.
This strikes me as very similar to the article where Twitter ditched Rails. The focus should be inward... how they chose a tool that didn't support their use case and how they solved the problem, but instead they're about the flaws (that aren't really flaws) of the tool.
It's always the craftsman.
- _Codemonkeyism 10y ago"1B+ rows in it with mysql?" Been there, really no fun.
- midom 10y agoAs 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.27.75/storage/rocksdb https://github.com/facebook/mysql-5.6/tree/webscalesql-5.6.2...
- _Codemonkeyism 10y ago"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?
- Swannie 10y agoThis is: "Split the index in your application code." And then do your joins, in your application code.
- deleted 10y ago[deleted]
- fasteo 10y agoPercona to the rescue [1]. Works flawlessly, at least in our case. [1] https://www.percona.com/doc/percona-toolkit/2.1/pt-online-schema-change.html https://www.percona.com/doc/percona-toolkit/2.1/pt-online-sc...
- maximegarcia 10y agohttps://github.com/soundcloud/lhm https://github.com/soundcloud/lhm Saved my life a few time :)
- _Codemonkeyism 10y agoThanks!
- barrkel 10y agoAm there right now, it's not really a problem - you just have to plan your schema changes and use Percona OST.
- _Codemonkeyism 10y agoThanks!
- Groxx 10y agoAlso 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.
- stubish 10y agoWhile the article is discussing PostgreSQL vs MySQL, Uber's actual win seems to be from switching their data model to their sharded Schemaless key=value store. I expect they would have got this win no matter what backend they chose for Schemaless.