grounded in: Rick Reed, Erlang Factory (2012 & 2014) · WhatsApp Encryption Overview whitepaper (2016) · WhatsApp Privacy Policy (store-and-forward, 30-day) · Signal / Open Whisper Systems (2014, 2016)
AlgoPlus//structures / case-study
Read the theory

Chat (WhatsApp)

Real-time messaging on Erlang/OTP + FreeBSD — persistent sockets, in-memory routing, store-and-forward, and Signal-Protocol E2EE.

Step
1/1
Phase
Legend
Design decision
Bottleneck
Solution added
AI Tutor Workspace
In a nutshell
Real systems aren't designed all at once — they grow. You start with the simplest thing that works (one server, one database), watch where it strains under load — the bottleneck — and add exactly one piece to relieve it: a cache, more servers behind a load balancer, a queue to do slow work in the background. Every box on the diagram earns its place by fixing a specific problem, trading a little added complexity for a concrete scaling win.
Ready
Press play to begin the cinematic walkthrough.
Real architectures aren't drawn all at once — they grow. Each component is added to kill one specific bottleneck, trading complexity for a concrete scaling win.
Key terms
Go deeper in the lesson
Read the full theory, intuition & complexity for Chat (WhatsApp).