Skip to main content

Classic Designs for System Designs

Classic designs are the recurring case studies used to practise system design. Social and content examples include a news feed, chat application and video platform, while infrastructure examples include a URL shortener, rate limiter and distributed cache. Each reveals trade-offs between fan-out, storage, ordering and latency.

Stage: Case Studies · Part of the System Design roadmap · Last reviewed 19 November 2026

What to learn in Classic Designs

Classic Designs interview questions

How would you generate unique short codes for a URL shortener?

Options include a counter encoded in base62, a distributed ID generator, or hashing the URL and handling collisions. A counter is simple and collision-free but needs coordination, so ranges can be handed to each app server.

What is the fan-out problem in a news feed?

When a user posts, followers need to see it. Pushing to every follower's feed makes reads fast but writes expensive for accounts with millions of followers. Many systems mix push for normal users with pull for celebrities.

Where Classic Designs fits in the System Design roadmap

Classic Designs belongs to the Case Studies stage (advanced level), which takes about 24 hours. Practise the interview.

Back to the full System Design roadmap