Scaling Datastores at Slack with Vitess
Slack's multi-year migration from active-active MySQL pairs to Vitess, so data could be sharded by any key, not only workspace.
For more teams that split data across many database servers, see our horizontal sharding case studies.
- Published
- 2020-12-01
- Scale
- 2.3 million QPS
- Techniques
- horizontal sharding database migration
- Stack
- MySQL Vitess
Try this stack yourself
- Railway · Deploy something like this on Railway: spin up MySQL plus your app in a few clicks. New accounts get $20 in credit (applied when you pick a paid plan).
Railway isn't part of Slack's setup in this story. It's just an easy place to try the same building blocks.
Some links above are affiliate links: if you sign up, How They Scaled may earn a commission at no extra cost to you. We only list tools that fit the stack in the story.