liveBook · Manning

Architectural quality

As explained in Grokking Software Architecture

Architectural quality is the set of system properties that characterize how well an architecture satisfies important operational and developmental objectives.

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

How Grokking Software Architecture covers it

How deep it goes
Defines core qualities and illustrates their costs with operational targets, without detailing implementation techniques.
Examples
Contrasts 99.999% with 99.9% availability and sub-50 ms with 800 ms response targets.
What you can do after
Evaluate quality tradeoffs by asking business stakeholders which properties matter most and what they will pay.
How it connects
Connects reliability, maintainability, scalability, performance, security, and testability to business priorities and architectural decisions.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.