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
Lead Time to Value	metric	Time to Market	The elapsed time from identifying an opportunity to delivering measurable benefit, which is usually dominated by waiting rather than by building.
Operational Readiness Go-Live Readiness, Launch Readiness	practice	Time to Market	Defining go-live from the whole value stream rather than from the deployment, so the processes that receive a launch - returns, reconciliation, support, tax - are ready before customers arrive rather than week…
Slip Cost per Week Weekly Delay Cost, Delay Cost per Week	metric	Time to Market	The money a launch loses for each week it is late - and whether that money is deferred or destroyed - which is the only form in which time to market can be traded against design quality.
Time to Market	concept	Time to Market	How long from idea to customer value — an architectural property determined by coupling, batch size and the number of teams required.