Approach for System Designs
The approach to system design starts before any boxes are drawn. It means clarifying functional and non-functional requirements, estimating traffic and storage with back-of-envelope arithmetic, defining the APIs clients will call, and sketching the core data model. These steps decide which architecture is reasonable.
Stage: Fundamentals · Part of the System Design roadmap · Last reviewed 19 November 2026
What to learn in Approach
- Separate functional requirements from latency, availability and consistency goals
- Estimate queries per second and storage using rounded numbers
- Define REST or RPC endpoints with sensible request and response shapes
- Model entities and relationships before choosing a database
- State assumptions aloud and confirm them with the interviewer
- Spot the read-heavy or write-heavy nature of a workload
Approach interview questions
Why do you estimate capacity before designing a system?
Rough numbers for requests per second, data size and bandwidth reveal whether one machine suffices or sharding and caching are needed. They stop you adding complexity the load does not justify, or missing it when it does.
What is the difference between functional and non-functional requirements?
Functional requirements describe what the system does, such as posting a message. Non-functional requirements describe qualities like latency, availability, durability and scalability, and they usually drive the major architectural choices.
Where Approach fits in the System Design roadmap
Approach belongs to the Fundamentals stage (intermediate level), which takes about 32 hours. Think in systems.
Other units in this stage
Back to the full System Design roadmap