Portfolio ↗

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
Business Case Structure practice Business Cases The argument format that gets technical investment funded — problem, options, quantified benefit, cost, risk and a recommendation.
Business Cases practice Business Cases The argument that an investment is worth making — where architects supply the cost, risk and option value rather than the enthusiasm.
Cash-Releasing Benefit Hard Saving, Budget-Line Saving concept Business Cases A benefit that reduces a named budget line on a known date, as distinct from released capacity or avoided cost - which are real but do not become money until a further decision is taken.
Cost of Inaction Cost of Delay, Do-Nothing Cost practice Business Cases The quantified ongoing cost of leaving a system as it is - the number that lets architectural work compete against feature work for funding.