RETURN TO SYSTEM DESIGN VAULT (55)BLUEPRINT #05 // Medium
#05MediumReal-Time & Stream Processing
Design Facebook Messenger or WhatsApp
ASKED IN INTERVIEWS AT:MetaUberTikTokAmazon
EXECUTIVE SUMMARY & PROBLEM STATEMENT
Design a real-time messaging system supporting 1-on-1 chats, group conversations, read receipts, offline message queuing, and end-to-end encryption.
SCALE ESTIMATION & TRAFFIC ENVELOPE
DAILY ACTIVE USERS / TPS1 Billion DAU, 100 Billion messages/day
READ / WRITE TRAFFIC RATIO1:1 bidirectional
5-YEAR STORAGE CAPACITYTransient Redis cache + Cassandra for long-term historical archives
FUNCTIONAL REQUIREMENTS
- [1]1-on-1 real-time messaging
- [2]Online/offline presence indicators
- [3]Read and delivery receipts
- [4]Offline message delivery
NON-FUNCTIONAL REQUIREMENTS
- •End-to-end delivery latency < 100ms
- •Guaranteed at-least-once delivery
- •Minimal battery/data usage on mobile
CORE ARCHITECTURAL COMPONENTS
Gateway Connection Managers (WebSockets)
Presence Service (Redis Cluster)
Session Store
Offline Message Queue (Kafka/RabbitMQ)
APNS/FCM Push Bridge
DATA SCHEMA & PERSISTENCE
Messages: message_id, conversation_id, sender_id, payload, status, timestamp
DISTRIBUTED TRADE-OFFS & FAILURE MODES
- ⟡Client-side storage with ephemeral server queues (WhatsApp style) vs Cloud-synchronized message history (Messenger/Telegram).