
From Laptop to Billions of Clicks: Designing a URL Shortener in 11 Steps
Blueprints of Scale — the anchor design
Blueprints of Scale is my public learning journal on system design. I'm Sarmeet — I build backend systems at scale, and I write to discover how things really work under the hood. Every post is plain-language, visual, and honest about what I know and what I'm still figuring out, with links to the best engineering writing out there for going deeper.

Blueprints of Scale — the anchor design
"Design Instagram" sounds like the friendly version of the social media question. Photos in, feeds out. Then you do the arithmetic and find three different hard problems sharing one name: a storage pr
Subtitle: Blueprints of Scale, Core Concepts #27 Section 1: The price that changed in one place and not in the other, in plain language This section is about a problem that sounds like bookkeeping and
Subtitle: Blueprints of Scale, Core Concepts #26 Section 1: The order that died between steps, in plain language This section is about work that takes longer than one request. A normal request lives f
Two copies of the same scheduler are running, which is exactly what you wanted. One copy was supposed to be insurance for the other. At midnight both copies wake up, both look at the same list of jobs
A checkout service is healthy at 9 AM. Traffic is steady, errors are near zero, and every dashboard is green. At 9:07 a partner launches a promotion and traffic triples in two minutes. The checkout se
Your service runs in one cloud region, a cluster of data centers in one metro area, and it runs well. Then the region has its bad day. It does not happen often, and it does not have to be a total outa
A database node stops answering. Ten seconds pass, then thirty. The cluster does what it was designed to do: it declares the node dead, promotes a replica, and starts copying data to a replacement. Th
A team builds an event ingestion service. The database passed every test in staging: clean API, sensible data model, queries that read well in review. In production it takes 200,000 writes a second fo