“-ilities” name the qualities that make a system good: how reliably it works, how easily it changes, how well it handles growth, and more. They give teams criteria for architectural decisions—but every quality has a cost in money and developer time. section 2.4 section 2.8
Common qualities include:
- Reliability: working correctly even when things go wrong. section 2.4
- Maintainability: making bugs easier to find and changes easier to understand. section 2.4
- Scalability: handling more users or load; performance: meeting speed, latency, and throughput needs. section 2.4
- Security, testability, and observability are also named as core qualities. section 2.4
These qualities compete for resources. Higher availability targets or faster response times require more investment, so the goal is not to maximize everything. Choose priorities that fit the business and make the tradeoffs explicit. section 2.4 section 2.12
Make the tradeoff visible
For a recommendation engine, prioritize performance and scalability, then explicitly defer maintainability for the first version and state that the initial algorithm may be complex. section 2.4.1
