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

6 terms shown.

Term	Kind	Topic	What it is
Feature Flags Feature Toggles	pattern	Feature Flags	Decoupling deployment from release, so code ships continuously and exposure is a runtime decision — with a lifecycle that must be enforced.
Flag Change Provenance Flag Audit Trail, Configuration Provenance	practice	Feature Flags	Recording who changed a flag, when, from what to what - and, separately, stamping the effective configuration version onto every artefact it influenced, because the first cannot reconstruct the second.
Flag Debt	concept	Feature Flags	The accumulating complexity of feature flags that are never removed, producing untested code paths and combinatorial behaviour nobody understands.
Flag Expiry Discipline Flag Lifecycle, Stale Flag Removal	practice	Feature Flags	Creating every flag with an owner and an expiry date and treating removal as part of the rollout's definition of done - because flags have a creation process and, without this, no removal process.
Knight Capital: $440 Million in 45 Minutes Knight Capital Incident	case-study	Feature Flags	A deployment that reached seven of eight servers, combined with a reused feature flag, activated dormant test code and destroyed the company in three quarters of an hour.
Release Toggle Temporary Feature Flag, Rollout Flag, Deploy-Release Decoupler	pattern	Feature Flags	A short-lived flag that decouples deploying code from releasing a feature, intended to be removed within weeks - and the category responsible for almost all accumulated feature-flag debt when it is not.