Skip to content
0:00 / 0:00

#slack#infrastructure#systemdesign

How Slack Works

InfoQ

234K subscribers • 69 videos on Hallway • Conference channel

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Keith Adams, Chief Architect at Slack

Intermediate. Assumes working knowledge.

162K views9 years ago1 recommendation

Distributed systemsSystems programmingSoftware architectureScaling and large-scale architectureNetworking and protocols

Keith Adams takes a tour of Slack's infrastructure, detailing how web and native clients interact with the backend and edge servers.

QCon San Francisco, the international software conference, returns November 17-21, 2025. Join senior software practitioners from early adopter companies as they share real-world insights and actionable advice to help you adopt the right technologies and practices. Gain exposure to innovative approaches and fresh ideas in software development and engineering, designed to inspire and challenge you. Don’t miss this chance to deepen your knowledge, sharpen your skills, and stay ahead in the ever-evolving world of technology. Register now: bit.ly/3BYzfbe -------------------------------------------------------------------------------------------------------------------------------------- Download the slides & audio at InfoQ: bit.ly/2z2fA57 Keith Adams takes a tour of Slack's infrastructure, from native and web clients, through the edge, into the Slack datacenter, and around the various services that provide real-time messaging, search, voice calls, and custom emoji. This presentation was recorded at QCon San Francisco 2016.

Why it's here

1 person recommends this

What people say. Recommended as an excellent real-world case study for learning system design and understanding scaling tradeoffs.

u/adamdevigiliSenior Software Engineerin r/ExperiencedDevs • Recommends

On “Improving system design skills for interviews”

For me, watching the people who actually built and scaled global-scale systems was really helpful, not just for the raw design info, but their mindset, approaches, tradeoffs, and cadence of how they approached problems. This Keith Adams talk about Slack is a good example. The InfoQ channel had a lot of good talks like these, but they can be a pain to find.