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
Correlated Degradation Demand-Coupled Failure, Peak-Correlated Dependency Risk	concept	Degradation Modes	The condition where a dependency's reliability worsens for the same reason that user demand rises, so the system is least capable exactly when it is most needed.
Degradation Ladder Kill Switch List, Feature Shedding Order, Brownout Plan	practice	Degradation Modes	An ordered, pre-agreed list of features that can be disabled under stress, each with a switch that works without deployment, a named owner, a trigger condition and a rehearsed fallback.
Degradation Mode	concept	Degradation Modes	A defined, intentional reduced state of service that the system enters under specified conditions, with known behaviour and known exit criteria.
Degradation Modes	concept	Degradation Modes	Explicitly designed operating modes below "fully working" — declared, testable, and switchable rather than emergent.