Read-heavy product catalog
2,000 req/s, 90% reads through a cache. At 20 s the cache is flushed.
What each component does hereGoals checked when the run ends
- ○Success ≥ 99%
- ○User experience (Apdex) ≥ 0.90
- ○p99 latency ≤ 300 ms
Keep success ≥ 99%, Apdex ≥ 0.90 and p99 ≤ 300 ms through the flush.
Try this
Read the design doc →Components 101
Each card is a component: a simulated piece of real infrastructure. Its shape says what it is; lines show who calls whom, and moving dots are live requests.
- Load balancer Spreads incoming requests over servers.
- Service Your code. Stacked cards are replicas.
- Cache Fast memory (Redis). Hits skip the database.
- Database The source of truth. Slow to scale.
- Queue Holds work for later; slots fill as it backs up.
- Stream An ordered log (Kafka) split into partitions.
- Object storage Files and media (S3).
- Model An AI model with quotas and response time.
- Security Shields that stop attacks before they land.
All components →