Terminology

2185 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 areas2185 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture89 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture81 Cost Architecture & FinOps66 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization66 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 concept785 practice729 pattern362 metric125 case-study77 tool62 protocol45

8 terms shown.

Term	Kind	Topic	What it is
Concurrency Limiting	pattern	Fault Isolation	Bounding the number of simultaneous in-flight operations so that overload produces fast rejection rather than resource exhaustion.
Durable Execution Workflow Persistence, Resumable Orchestration	pattern	Reliability & Resilience	Persisting a workflow's progress outside the process executing it, so that worker restarts, deployments and crashes resume from the last completed step rather than losing position.
Failover	pattern	Failover	Switching to a standby when the primary fails — where detection, fencing and the decision to automate are harder than the switch itself.
Failover Orchestration	pattern	Failover	The sequence of detection, decision, promotion and traffic redirection that moves service from a failed component to a healthy one.
Graceful Degradation in Practice	pattern	Graceful Degradation	Deliberately reducing functionality to preserve the core when a dependency fails — a product decision expressed in architecture.
N+1 and 2N Redundancy	pattern	Redundancy	Provisioning one spare beyond required capacity versus provisioning double, and the failure assumptions each encodes.
Pre-Provisioned Capacity	pattern	Static Stability	Running capacity that is already in place to absorb a failure, rather than depending on a control plane to create it during the failure.
Value-Graduated Fallback Tiered Degradation by Stake, Risk-Weighted Fallback	pattern	Graceful Degradation	A degradation ladder whose depth depends on the value at stake, so a low-value transaction proceeds on weak signals while a high-value one fails closed - replacing a single binary decision that is always wrong…