CSE Roadmap

Core tier · about 3 hours · 9 parts

Part 4 of 9 · 2 min read

Step 2: A high-level design

The next ten to fifteen minutes: boxes, arrows, numbers and a first walk through.

Think of a city map before street detail. Highways and districts come first. House numbers come last.

Step 2 takes about 10 to 15 minutes. The aim is a simple blueprint that the other person agrees with, before anyone goes deep.

  1. Draw boxes for the main parts: clients, servers, data stores, caches, queues, a content delivery network. Keep the picture small, about six to ten boxes.
  2. Draw arrows for the main flows, and label them: "upload photo", "read feed".
  3. Do a few estimates from module 3 to check the blueprint fits the scale. Say out loud when and why you are calculating.
  4. Walk through two or three real cases with the drawing: "A user posts a photo. The request goes here, then here." A walk through often reveals a missing box or an edge case.
  5. Ask for feedback. Treat the listener as a teammate and invite correction: "Does this match what you had in mind?"

Whether to include the API and the data tables depends on the problem. For a huge problem such as a search engine, that level of detail is too low for step 2. For a small backend, such as the server of a multiplayer game, it fits. Ask.

Read it as

The high-level design is a proposal. The goal of step 2 is agreement, not completeness. A blueprint both sides agree on, even if it is rough, is worth more than a polished one that nobody checked.

A simple layout for the whiteboard helps. Put clients on the left, servers in the middle and data stores on the right, and flow arrows from left to right. A reader then follows it like a sentence.

Check yourself:

  • Why walk through concrete cases and not only look at the boxes?
  • How many boxes is a good size for a first drawing?