Design a URL shortener that handles 100k reads a second. What breaks first?
20:00
Sketch as you talk. Boxes and arrows are plenty.
Time · 20:00 used
Your design broke first at the database.
At 100k reads a second, every redirect went to one database. Its reads run out long before the rest of the system does, and one viral link puts the whole load on a single key.
Sample result · Your own appears here once the interviewer is connected
What happened
04:30You put every redirect on one database and didn't size the reads.
07:00You added a cache, but had no answer for a miss storm.
10:00The viral link landed on one cache node, and you didn't spread it.
The pattern to work on
Caching
Keep the same read off the database: size the hit rate, guard against miss storms, and spread hot keys. It's one of the 14 patterns in a full rehearsal.
Two weeks of this, fitted to your date.
Hold Your Level is ten timed mocks like this one, against the same interviewer, with a straight call by day 5: go, or move the date. $249, paid once.