How Slack rearchitected its system to achieve zero downtime and improve latency, reliability and availability



How Slack rearchitected its system to achieve zero downtime and improve latency, reliability and availability

How Slack rearchitected its system to achieve zero downtime and improve latency, reliability and availability


Video description

In 2016, Slack faced a problem: the load on its backend servers had increased by 1,000x. Bing Wei explains how rearchitecting the system with lazy loading, a publish/subscribe model, and an edge cache service overcame the problem with zero downtime, improved latency, and gains in reliability and availability.


Table of Contents

How Slack rearchitected its system to …


Start your Free Trial

Self paced

Go to the Course
We have partnered with providers to bring you collection of courses, When you buy through links on our site, we may earn an affiliate commission from provider.