SYSTEM DESIGNDesign a Code Deployment System (CI/CD)GitHubVercelHeroku
TRAFFIC LEVEL
—/3
CONSTRAINTS
Concurrent builds10,000
Avg build time3 minutes
Build isolationOne Docker container per build
Rollback time< 60 seconds
Deployment strategyBlue-green or rolling update
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
GitHubVercelHeroku

Design a CI/CD system that automatically builds, tests, and deploys code on every git push. Support 10,000 repositories pushing code simultaneously, build isolation (each build in its own container), and zero-downtime deployments with instant rollback.

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