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

3 terms shown.

Term	Kind	Topic	What it is
Peak Multiple Headroom Multiple, Peak-Over-Peak Factor	metric	Estimation	The factor by which a system is sized above its last observed peak - a fast planning heuristic that silently assumes the population generating load is the population you served before.
Physical Latency Floor Speed-of-Light Budget, Propagation Floor	metric	First-Principles Reasoning	The minimum achievable round-trip time between two locations set by propagation in fibre - roughly 1 ms per 100 km each way - which no provider, protocol or cache can improve on for a request that must reach t…
Unit Cost Ceiling Cost per Transaction Limit, Infrastructure Cost Budget per Order	metric	Business Understanding	The infrastructure cost per transaction that the business model can bear, derived from contribution margin and fixed before design, which decides how much work a request is allowed to do.