Terminology

2185 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 areas2185 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture89 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture81 Cost Architecture & FinOps66 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization66 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 concept785 practice729 pattern362 metric125 case-study77 tool62 protocol45

9 terms shown.

Term	Kind	Topic	What it is
Abuse Case Misuse Case	concept	Communicating Threat Models	A use case written from the attacker's side - a hostile actor plus the interaction that achieves their goal - which engineers can refute or fix, unlike a likelihood-impact score which they can only dispute.
Data Lineage View	concept	Data-Flow Diagrams	A view showing how data moves and is transformed through a system, independent of the components that do the moving.
Deployment Topology View	concept	Deployment Diagrams	A diagram showing where software actually runs — regions, zones, networks and hosts — which is where availability and cost properties become visible.
Diagram Altitude	concept	Architecture Diagrams	The level of abstraction a diagram commits to, and the rule that mixing levels in one picture makes it useless to every audience.
Diagram Maintenance Economics Which Diagrams to Keep, Stale Diagram Cost	concept	C4 Model	The rule that a diagram earns its maintenance cost only when it explains something hard to derive from source - which is why structure diagrams below the container level should be generated or absent.
Documentation Decay	concept	Documentation Practice	The tendency of written documentation to become inaccurate faster than it is updated, making stale documentation actively more harmful than none.
Evidence Transferability Context Matching, Scale Applicability, Case Study Fit	concept	Explaining Trade-offs	The degree to which a finding from another organisation's system applies to yours, determined by similarity of workload shape, scale and constraints - and the discipline of extracting the question rather than …
SLA Measurement Point Measurement Boundary, Observation Point	concept	Negotiation	The place in the request path where an availability or latency commitment is observed, which decides what the number means and is where nearly every SLA dispute actually originates.
System Context Boundary	concept	Context Diagrams	The line separating what a project owns and can change from what it must integrate with and accept as given.