Design Slack

Problem framing: a multi-tenant workspace platform

Slack is a workplace collaboration platform, and the single fact that organizes the whole design is multi-tenancy: every piece of data and traffic is scoped to a workspace, and workspaces range from a five-person startup to a half-million-seat enterprise on the same shared infrastructure. So the spine is not just chat — it is per-workspace isolation, channels (public and private) and DMs and threads, real-time fan-out with presence, full-text search across messages and files, and an app platform of slash-commands and bots. Unlike WhatsApp, Slack is deliberately server-readable: the workplace wants search, link previews, retention, and compliance export, so content lives in plaintext under strong access control, not end-to-end encryption.

State the multi-tenant framing up front. Every later decision — sharding by workspace, fan-out within a channel, a per-workspace search index, noisy-neighbor isolation, enterprise compliance and eDiscovery — follows from the unit of everything being the workspace. The hard parts are isolating wildly different-sized tenants on shared infrastructure, fanning a message to every channel member and their devices in real time, and making years of a workspace's history instantly searchable.