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

3 terms shown.

Term	Kind	Topic	What it is
Attack-Path Framing Path-Based Finding, Attack-Path Finding Format	practice	Communicating Threat Models	Writing each security finding as a reachable path from entry point to impact with the one change that removes it and the cost of that change, replacing severity scores that can be argued with instead of acted on.
Communicating a Threat Model	practice	Communicating Threat Models	Producing a threat model that engineers act on — structured by data flow, prioritised by risk, and expressed as work rather than as a report.
Trust Boundary Diagram	practice	Communicating Threat Models	A diagram marking where data crosses between zones of differing trust, which is the structure a threat model is built on and the form security findings are best communicated in.