Pinterest
Why Pinterest Bet on Sharded MySQL Over NoSQL
Pinterest hit early scaling walls, tried NoSQL alternatives, then built ID-encoded sharded MySQL instead — and it outlasted the exotic options.
3 min read
Tag
3 articles
Pinterest hit early scaling walls, tried NoSQL alternatives, then built ID-encoded sharded MySQL instead — and it outlasted the exotic options.
Why Uber built Schemaless, an append-only document layer on top of sharded MySQL, instead of migrating wholesale to a NoSQL database.
Why Slack adopted Vitess to shard MySQL horizontally at the connection-pooling and proxy layer instead of migrating off relational storage entirely.