←SYSTEM DESIGNDesign a Distributed Message Queue (Kafka)LinkedInConfluentAmazon
TRAFFIC LEVEL—/3
CONSTRAINTS
Write throughput1M messages/sec
Avg message size1 KB
Write bandwidth~1 GB/sec
Retention7 days
Storage needed~600 TB
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
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
🚨 INCIDENT
LinkedInConfluentAmazon
Design a durable, distributed message queue that supports 1M messages/sec write throughput, at-least-once delivery guarantees, consumer groups with offset tracking, and message retention for 7 days.