Terminology

2205 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 areas2205 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture94 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture86 Cost Architecture & FinOps71 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization71 AI-Era Architecture69 Software Architecture & Engineering71 Architecture Patterns71 Architecture Decision-Making63 The Architect's Meta-Skills61 Delivery & Release Engineering66 Platform Engineering & Developer Experience70 Testing & Quality Architecture66 Data Platform Architecture64 Streaming & Real-Time Data69 Data Governance & Semantics69 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk64

Kind Any concept794 practice734 pattern368 metric125 case-study77 tool62 protocol45

4 terms shown.

Term	Kind	Topic	What it is
Assumption Excavation	practice	First-Principles Reasoning	Deliberately surfacing the unstated beliefs behind a design or a requirement, to test which are constraints and which are merely habits.
First Principles Thinking	practice	First-Principles Reasoning	Reasoning from what must be true rather than from what is usually done — the technique for problems where precedent is unavailable or misleading.
Precondition Audit Pattern Fit Check, Applicability Test, Assumption Check	practice	First-Principles Reasoning	Explicitly stating the conditions a pattern assumes and checking each against your situation - which is where pattern matching becomes judgement rather than recall.
Precondition Check Pattern Assumption Test, Does This Fit	practice	First-Principles Reasoning	Testing whether a problem's conditions match the assumptions a familiar pattern encodes - the ten-minute exercise that separates useful pattern reuse from cargo-culting.