ByteByteGo System Design Newsletter

What you get

The newsletter is free to subscribe to. Every Saturday, all subscribers receive an issue that usually bundles several short, illustrated explanations: a protocol, a database concept, a comparison of API styles, a cheat sheet, or how a known product handles a request. Past topics include database types, SOLID design principles, what happens when you press play on Netflix, CI/CD, authentication and high availability.

A paid subscription adds an extra deep dive every Wednesday and a say in which topics get covered. Check the Substack page for the current price.

Why the format works

System design is spatial. A diagram that shows where the cache sits relative to the database and the queue conveys in seconds what several paragraphs struggle with. Seeing one or two of these a week, over months, gives you a large set of patterns to recognise and draw on when you meet a new system at work or in a design discussion.

The archive is also searchable. When you need a quick refresher on, say, the difference between a forward and reverse proxy, there is often a single diagram that covers it.

How to use it without it becoming noise

• Skim each Saturday issue and save only the one or two diagrams relevant to what you are learning or working on.
• When a diagram names a technology you do not know, spend ten minutes on its official docs. The newsletter points; it does not teach in depth.
• Once a month, redraw three saved diagrams from memory. If you cannot, you did not really learn them.
• Do not treat it as a curriculum. A stream of interesting topics never adds up to a structured understanding, and it is easy to feel productive while only scrolling.

Pair it with

• A structured course or book for order and depth, such as the System Design Interview books or Designing Data-Intensive Applications
• The free System Design 101 repository from the same team, which collects many of these diagrams by topic
• Company engineering blogs in this library, for the full story behind real architectures

Common questions

Is the free tier enough? For most readers, yes. The Saturday issue carries the diagrams people share. The paid deep dives are longer and useful if you want more depth each week, but a book gives more depth per rupee or dollar.

How long does each issue take? A few minutes to skim, fifteen to twenty if you read every item closely.

Is it good for beginners? The diagrams are approachable, but they assume you know basic terms like load balancer, cache and database index. If those are unfamiliar, start with a fundamentals course and come back.

Is it only about interviews? No. Most issues explain how real systems and tools work, which is as useful in a job as in preparation for one.

Best for: students and engineers who want a weekly, visual habit that keeps system design concepts fresh.