InterviewForge

Design WhatsApp (Chat Messaging)

A deep design of a chat system like WhatsApp: connection management, delivery guarantees, group chat fan-out, presence, and end-to-end encryption implications.

Updated 2026-09Hard

Requirements & scope

  • Functional: 1:1 and group chat, send text/media, offline delivery, read receipts, last-seen, typing indicators.
  • Non-functional: low-latency delivery, high availability, messages must not be lost, end-to-end encrypted (E2EE).
  • Scale: ~2B users, ~100B messages/day, mostly small groups (<=256).
  • Consistency: per-conversation ordering is required; global ordering across conversations is not. Delivery is at-least-once with client dedup (effectively exactly-once).

Out of scope (covered in detail below)

Voice/video calls, status/stories, the E2EE key-exchange protocol, backups, and media (photos/video) — deferred and discussed in the dedicated section.

Unlock the full guide

Premium members get every DSA, system design, company and role interview guide — plus AI practice, mock interviews, and analytics.

Unlock with Premium