![]() ![]() ![]() “Vitess has been a clear success for Slack,” says Demmer. “ Vitess was really the only approach that fit all our needs,” says Principal Engineer Michael Demmer. They didn’t want to move away from MySQL, and they wanted to continue to host Slack’s own instances running in AWS, on a platform that incorporated new technology now, but could still be extensible later. In looking for a scalable storage solution, the team had certain requirements. The Slack engineering team knew it needed a new approach to scaling and managing databases for the future. And the burden of manually managing the fleet of hosts in the legacy configuration was taxing the operations teams. The company’s busiest database hosts had to handle all the queries from larger and larger customers, so they were running hotter and hotter while there were thousands of other hosts that were mostly idle. In the fall of 2016, Slack was dealing with hundreds of thousands of MySQL queries per second and thousands of sharded MySQL hosts in production. ![]() How Slack leverages Vitess to keep pace with ever-growing storage needs Challenge ![]()
0 Comments
Leave a Reply. |