Architecture Diagram Example

Architecture diagrams of well-known systems and the reasoning behind them

Examples

How it works

  1. Pick a system from the grid.

  2. Start with the diagram, then read why it looks this way: requirements, load numbers, key decisions and trade-offs.

  3. Ask a question about the design at the bottom of the breakdown.

Questions

Which systems are covered?

Six for now: a URL shortener, Twitter, Uber, a web crawler, a search engine and a notification service.

Are these the real architectures of Twitter and Uber?

No. They are teaching designs for systems of that kind. The production systems of those companies are larger and change all the time.

How do I read a diagram?

Boxes are services, cylinders are data stores, a dashed outline is something outside your system. Thick arrows show the path most requests take. Dashed arrows show work that happens later, such as sending a notification.

Why does every example come with numbers?

The numbers decide the design. 40 writes a second fit on one database server. 400,000 need a different design.

Can I start my own diagram from an example?

Yes. Open the Architecture Diagram tool, describe your system and name the example you want to start from.

More tools