ScaleCrafts

Scenario system design problems

3 problems where scenario is a core concern. Draw the architecture, explain your choices, and see how an interviewer would score it.

3 problems
StatusProblemTopicsDifficultyBestLists
Scenario: the database is at 95% CPU

A product catalogue API runs on one MySQL server. Traffic has grown to 30,000 reads a second, database CPU sits at 95% and p99 latency has climbed from 50 ms to 2 seconds. Bring latency back down, and keep it down as traffic doubles.

ScenarioRead scalingCachingEasy
Scenario: a slow payment provider takes the site down

Checkout calls a third-party payment provider. During the evening peak its responses slow from 200 ms to 30 seconds. Requests pile up waiting on it, and within minutes even browsing and search stop responding. Redesign so one slow dependency can’t take the whole site down.

ScenarioResiliencePaymentsMedium
Scenario: a flash sale brings 10,000 requests a second

An online store’s traffic is usually a fiftieth of what it’s about to get. At noon a flash sale opens on 5,000 discounted phones and traffic jumps to 10,000 requests a second for 30 minutes. Every shopper must get an answer, not one phone may be oversold, and the rest of the store must keep working.

ScenarioTraffic spikesInventoryHard