Read-heavy system design problems
6 problems where read-heavy is a core concern. Draw the architecture, explain your choices, and see how an interviewer would score it.
6 problems
| Status | Problem | Topics | Difficulty | Best | Lists |
|---|---|---|---|---|---|
| Design a URL shortener Build a service like bit.ly that turns long URLs into short links and redirects visitors to the original address. | HashingCachingRead-heavy | Easy | |||
| Design Pastebin Let users paste text, get a short link and share it, like Pastebin or GitHub Gist. | Object storageCachingRead-heavy | Easy | |||
| Design a weather API Serve current weather and forecasts for any location to millions of apps, using data bought from upstream providers. | CachingThird-party dataRead-heavy | Easy | |||
| Design a comment system Add threaded comments to any web page, with replies, likes and moderation, like Disqus. | ThreadsModerationRead-heavy | Easy | |||
| Design search autocomplete Suggest the top completions as a user types into a search box, like Google’s autocomplete. | TriesCachingRead-heavy | Medium | |||
| Design Yelp Find nearby restaurants and businesses, read reviews and see ratings, like Yelp. | GeospatialSearchRead-heavy | Medium |