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
Captive User Signal Mandated Tool Measurement, Workaround Count	metric	Product Thinking	The small set of measurements that still carry information when users cannot choose an alternative - workarounds, time to first success, abandonment - because usage and satisfaction no longer do.
Guarantee Surface Promise Surface, Service Guarantee Footprint	concept	Product Thinking	The set of customer-facing promises a product has made, each of which obliges the architecture to detect its own breach and pay for it - so this surface, not the feature count, drives a whole class of build cost.
Outcome over Output	concept	Product Thinking	Measuring and committing to changes in user or business behaviour rather than to the delivery of features.
Product Thinking	concept	Product Thinking	Treating what you build as something with users whose problems it must solve — applied to internal platforms as much as to customer-facing products.