4 ms·
20TB of data and 10k/s of transactions is not a large cluster. There are Vitess cutters with petabytes of data and 100s of millions of users doing millions of Q
by samlambert 4y ago
20TB of data and 10k/s of transactions is not a large cluster. There are Vitess cutters with petabytes of data and 100s of millions of users doing millions of QPS.
The largest Vitess cluster we know of runs on 10s of thousands of servers. So "False, just completely false" is dramatic.
Slack is powered by Vitess https://slack.engineering/scaling-datastores-at-slack-with-vitess/ https://slack.engineering/scaling-datastores-at-slack-with-v...
Twitter runs Vitess https://blog.twitter.com/engineering/en_us/topics/infrastructure/2023/how-we-scaled-reads-on-the-twitter-users-database https://blog.twitter.com/engineering/en_us/topics/infrastruc...
I am sorry you had a buggy experience running Vitess yourself but you just wrong about the size of these production workloads.
- billythemaniam 4y agoI didn't claim that I am dealing with a gigantic workload (total QPS is a lot higher btw). Rather I claimed we are at the point where a distributed database is a good idea if the business wants to continue to scale without major database trouble. I gave the specs so others can understand the parameters of the evaluation. If Vitess didn't perform well at that scale, I can't imagine the pain at Slack and Twitter scale. I don't envy them at all.
- samlambert 4y agohttps://twitter.com/stewart/status/1252385972014088194 https://twitter.com/stewart/status/1252385972014088194 They are pretty happy! Different people find different things difficult. Don't feel bad.
- billythemaniam 4y agoI don't. I am very happy to not use Vitess and more than willing to recommend your competitors. Don't feel bad.
- pradeepchhetri 4y ago> There are Vitess cutters with petabytes of data. Is it GitHub? Where can I find more details about them? It will be interesting to read more about it.