Architectural quality describes how well a system meets important operational and developmental goals. The “-ilities” are a menu of qualities to weigh—not a checklist to maximize without regard to cost. section 2.4
Common qualities ask whether a system can:
- Keep doing the right thing when things go wrong (reliability). section 2.4
- Make bugs easier to find and changes easier to understand (maintainability). section 2.4
- Handle more load (scalability) and respond quickly or process more work (performance). section 2.4
- Protect data and prevent unauthorized access (security), and make correctness easy to verify with tests (testability). section 2.4
Quality has a price
Targeting 99.999% availability rather than 99.9%, or responses under 50 ms rather than 800 ms, takes more investment. Ask which qualities matter most and what the business is willing to pay. section 2.4
