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
Budget Guardrail	practice	Cost Governance	An automated control that constrains or alerts on spend before an invoice arrives, rather than reporting overspend after the fact.
Cost Governance	practice	Cost Governance	The guardrails, budgets and approval structures that prevent cost surprises without becoming a bottleneck.
Cost Telemetry Lag Billing Data Delay, Spend Reporting Latency	concept	Cost Governance	The delay between spend being incurred and appearing in billing data, which sets a floor on how fast any detective cost control can possibly react and explains why budget alerts arrive after the money is gone.
Elastic Cost Blindness Soft Constraint Failure, Invoice-Delayed Feedback	concept	Cost Governance	The failure mode of elastic platforms - the system satisfies any request rather than refusing it, so a capacity problem becomes a cost problem that reports itself a month late.