Skip to content

Famous systems

Classic designs you can load-test.

Simplified, healthy architectures for well-known kinds of apps. Open one, change one thing, and see why every component is there.

like bit.ly or TinyURL

URL shortener system design

Creating a short link is rare; following one is constant. Reads outnumber writes many times over.like WhatsApp or Telegram

Chat app system design

Sending a message is a write, and people send a lot of them, so writes are a big share of traffic.like X (Twitter) or LinkedIn

News feed system design

People scroll far more than they post, so the feed is read-heavy.like YouTube or Netflix

Video streaming system design

Almost all traffic is video chunks, which never change once uploaded: perfect for a CDN.like a concert ticket drop or a Big Billion Days sale

Flash sale system design

Everyone arrives at the same second, and many of them try to buy (write) at once.like Uber or Ola in one city

Ride hailing system design

Every active driver sends a location update every few seconds, so most traffic is writes.like Instagram or Pinterest

Photo sharing system design

Most requests are images, served from the CDN, so your servers never see them.like Google search suggestions

Search autocomplete system design

Every keystroke is a request, and it must answer in well under 100 ms to feel instant.like UPI or Stripe checkout

Payments system design

Correctness beats speed: a payment must be recorded exactly once, before the user is told it succeeded.like LeetCode or Codeforces

Online code judge system design

Browsing problems is cached reads; submitting code is the expensive part.