Re:Scaling Datastores at Slack with Vitess
by ahachete on Monday December 07, 2020 @12:33PM
(#25334467)
Cannot edit any longer, but yes, that's a typo, it's 300K QPS.
Right now the cluster is only 8 instances, and the write-only traffic on the master spikes to 70K QPS.
So I agree with you --pretty beefy hardware, and it'd probably require sharding before reaching Slack's scale, but still quite impressive.
Slack are getting 300K WRITES per second, though. Which does mean you have really no choice but to shard - read replicas are nice for scaling reads, but do nothing for writes, and that’s A LOT of writes.