Terminology

454 terms, tools, patterns and metrics an architect is expected to use precisely. Each one gets a short explanation of what it is, and — where it matters — what it is commonly confused with. Search filters as you type; the column headers sort.

All areas454 Architecture Fundamentals16 Distributed Systems73 Data Architecture71 Cloud Architecture55 Networking13 API & Integration Architecture17 Reliability & Resilience16 Observability14 Performance & Capacity Engineering13 Security Architecture50 Cost Architecture & FinOps12 Business Architecture9 Architecture Communication8 Enterprise Architecture8 Legacy Modernization11 AI-Era Architecture15 Software Architecture & Engineering19 Architecture Patterns15 Architecture Decision-Making11 The Architect's Meta-Skills8

Kind Any concept166 practice107 pattern93 case-study26 tool26 protocol22 metric14

8 terms shown.

Term	Kind	Topic	What it is
Constraint Thinking	practice	Meta-Skills	Designing for the budget, timeline, skills, regulations and existing estate that actually exist, rather than for the ones a textbook assumes.
Decision-Making Under Uncertainty	practice	Meta-Skills	Choosing well when the information is incomplete — by bounding the downside and buying information, rather than by waiting for certainty.
Failure Thinking	practice	Meta-Skills	Making "what happens when this fails?" a standing question applied to every component and every dependency in a design.
First-Principles Reasoning	practice	Meta-Skills	Reducing a problem to the physical, mathematical or economic facts it rests on, then reasoning up, rather than reasoning from analogy or convention.
Pattern Recognition	practice	Meta-Skills	Recognising that a novel-looking problem is an instance of one you have seen before, and knowing which parts of the previous solution transfer.
Pragmatism	practice	Meta-Skills	Preferring the simplest architecture that satisfies the requirements, and treating additional structure as a cost that must be justified.
Systems Thinking	practice	Meta-Skills	Reasoning about a system in terms of the interactions and feedback loops between its parts, rather than the parts individually.
Trade-off Analysis	practice	Meta-Skills	Making the costs of an architectural choice explicit and comparable, rather than presenting a recommendation as if it were free.