SYSTEM DESIGNDesign an Email Service (Gmail)GoogleMicrosoftProton
TRAFFIC LEVEL
—/3
CONSTRAINTS
Active users1B
Emails sent/day300B
Avg email size75 KB
Peak ingest rate1M emails/sec
Storage per user15 GB free
Compute & Network
Load BalancerDistribute traffic
API GatewayEntry point / auth
API ServerBusiness logic
Worker NodeAsync processing
CDN EdgeGlobal cache
WebSocket GatewayPersistent connections
Data Stores
PostgreSQLRelational DB
MySQLRelational DB
CassandraWide-Column DB
DynamoDBNoSQL / Managed
S3 BucketObject storage
Queues & Cache
Redis CacheIn-memory store
KafkaEvent stream
ZookeeperCoordination
Specialized
Bloom FilterProbabilistic set
Rate LimiterThrottling
Geohash ServiceGeospatial index
Trie ServerPrefix search
APNS / FCMPush notifications
AggregatorBatch / roll-up
Drag to canvas · Hover node for × to delete · Draw from handle to connect
Design your architecture
Drag components from the left panel · Connect them by drawing from a node handle · Hit Start Simulation to validate
🚨 INCIDENT
GoogleMicrosoftProton

Design a large-scale email service supporting 1B+ users. Support sending, receiving, threading, search across 15 years of email history, spam filtering, and storage for users with 50GB+ of email. Handle 1M emails/second at peak (spam storms).

📥 Assigned to:You — Senior Engineer
SCALE LEVELS
1
10,000 RPS
Target: <500ms
2
100,000 RPS
Target: <200ms
3
1,000,000 RPS
Target: <100ms
GLOBAL SUCCESS RATE
100.0%
P99 LATENCY
45ms
Target: < 200ms
TOTAL RPS INGESTED0 / 11,000
EngPrep — Real Engineering. Real Interviews.