System design
- Parts
- 07
- Minutes to read
- 66
Architecture starts with constraints. This series builds a way to reason about a system: what to ask, what to measure, where failures may occur, and how to revisit decisions after launch.
The articles themselves are published in Russian.
What you will explore
- Translate business requirements into load, latency, and acceptable data loss.
- Describe write, read, and processing flows together with their accumulation points.
- Choose feedback mechanisms and assess decisions against production behavior.
Reading order
Start with the introduction and read in order. Each part builds on the questions raised by the previous one.
- 01System Design 0: It Is More Than BoxesAn introduction to system design as work with requirements, data flows, feedback, and system evolution.8 min
- 02System Design 1: It Starts with QuestionsHow to turn a vague business request into measurable requirements and avoid designing a system for the wrong problem.10 min
- 03System Design 2: Three Pillars of ArchitectureHow to balance reliability, scalability, and maintainability when improving one property makes the others more expensive.9 min
- 04System Design 3: Design the Data FlowsWhy a living architecture models writes, reads, and background processing as flows with distinct rates and constraints.14 min
- 05System Design 4: Feedback LoopsHow backpressure, rate limits, priorities, and circuit breakers turn overload from a total outage into controlled degradation.14 min
- 06System Design 5: Do Not Hammer Nails with a MicroscopeHow to choose a technology stack from requirements and first principles instead of hype, habit, or a fashionable tool list.5 min
- 07System Design 6: Architecture Has No Finish LineWhy production starts another design cycle as metrics, incidents, and new requirements continuously reshape the system map.6 min