Scaling Datastores at Slack with Vitess
From the very beginning of Slack, MySQL was used as the storage engine for all our data. Slack operated MySQL servers in an active-active configuration. This is the story of how we changed our data storage architecture from the active-active clusters over to Vitess — a horizontal scaling system for MySQL. Vitess is the present…
Discussion around the web
- Hacker News99 · 34 💬
Score breakdown
- Technical depth59
- Practical value90
- Originality85
- Writing quality100
- Source reputation85
- Recency0
- External engagement29
- On-site engagement0
More like this
Shopify Engineering64
We replaced Redis with MySQL for inventory reservations—and it scaled (2026) - Shopify
unknown·12 min read
Shopify Engineering51
How to Reliably Scale Your Data Platform for High Volumes - Shopify
unknown·12 min read
Engineering at Meta51
DCPerf: An open source benchmark suite for hyperscale compute applications
unknown·6 min read
Discord Engineering35
How Discord Automates ScyllaDB Clusters at Scale
unknown·1 min read
Engradar shows a summary and links to the original article. The full article is hosted on slack.engineering.