system design
The work of deciding how the parts of a software system fit together to meet its requirements, and writing down what each choice costs.
In more detail
A system design names the load, where data lives, and what happens when a part fails, before it names any product. The diagram is only a summary; the real output is a set of decisions with the options that were rejected. This course treats every design as a list of trade-offs you can defend with numbers.
Related terms
- trade-off — A choice that gains one property by giving up another, such as speed bought with staleness.
- decision record — A short written note of a technical decision, the facts behind it and the trade-off accepted, so later reviewers understand why.
- non-functional requirement — A measurable promise about how well a system works, such as how fast, how available, or how durable it must be.
- failure mode — A specific way a system or component can break, described by its symptom, its cause and what users experience.
Taught in
- What A Design Is For, And How To Run A Design Discussion — Scalable System Design & Distributed Architecture
- The Storage Decision: Relational Versus Document — Scalable System Design & Distributed Architecture