Persist first
Messages should be durably written before delivery fanout so transient socket failures do not become message loss.
Free WhatsApp breakdown
How to answer Design WhatsApp in a system design interview.
WhatsApp is not just “messages in a database plus WebSockets.” Strong answers separate durable message history from ephemeral connection state and explain what guarantees matter for delivery.
Free to share
Targets "Design WhatsApp"
No signup wall
Center of gravity
Delivery semantics before features.
Durable storage
Session routing
Offline sync
The pivot
Separate message durability from connection state.
Weak answers treat messaging as one system. Strong answers split it into at least two: durable message history and transient device/session state. That is the difference between “chat app” talk and production messaging reasoning.
Route by session
Online devices need fast session lookup and receipt handling, but session state should not be treated like durable truth.
Recover with sync
Offline devices need cursor-based catch-up instead of relying entirely on real-time delivery.
30-second answer shape
What a stronger answer sounds like.
Open with the system split
“I would separate durable message storage from ephemeral connection and presence state, because those have different latency and correctness needs.”
Define the guarantees
“I care about not losing messages, preserving conversation ordering where it matters, and letting offline devices catch up via cursor-based sync.”
Close with tradeoffs
“Presence can be soft-state, but message durability cannot. I would accept eventual consistency in presence to keep the delivery path fast.”
Common mistake
Do not reduce WhatsApp to WebSockets plus storage.
Wrong start
“Users connect by WebSocket and messages are stored in a database.” That skips the product guarantees people actually expect.
Better start
“The hard part is delivering messages with low latency while preserving durability, online/offline recovery, and conversation-level ordering.”
Why it wins
The interviewer hears that you understand messaging as a guarantee problem, not just a transport problem.
Want the full version?
The paid WhatsApp book goes deeper on real-time delivery architecture.
The full breakdown covers receipts, sync cursors, multi-device support, session routing, ordering, retries, and how to defend delivery tradeoffs cleanly in an interview.