Part 2 of 9 · 1 min read
Three goals
The three qualities of a good system, in one plain line each.
Think of a bridge. A good bridge does not collapse when a truck is heavier than expected (reliable). It still works when traffic grows from 100 cars a day to 100,000 (scalable). And a repair crew can inspect, fix and widen it without closing it for a year (maintainable).
A software system needs the same three qualities.
Reliability
A system is reliable if it keeps working correctly, at the expected speed, even when things go wrong: broken parts, human mistakes, unexpected input.
Example: an online shop keeps taking orders correctly even while one of its servers crashes.
Scalability
A system is scalable if it keeps working well as it grows, in users, in data or in the number of requests, by adding resources in a sensible way.
Example: a shop that works with 1,000 customers a day and still works, after adding more servers, with 1,000,000.
Maintainability
A system is maintainable if many different people can work on it over the years, fixing problems, running it and adding features, without great pain.
Example: a new engineer on the shop team fixes a bug in the first week and adds a small feature in the second.
Scalability is not a yes-or-no label. "Is it scalable?" is the wrong question. The right question is "If the load grows in this particular way, what must be added, and how hard is it?"
Check yourself:
- Which goal does a daily backup serve most directly?
- Which goal is at risk when no one remembers why a part of the system exists?