Terminology

2225 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 areas2225 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 Architecture74 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 Architecture69 Streaming & Real-Time Data69 Data Governance & Semantics74 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk69

Kind Any concept801 practice736 pattern377 metric127 case-study77 tool62 protocol45

5 terms shown.

Term	Kind	Topic	What it is
Anomaly Retention Keep the Weird Records, Realistic Test Data	practice	Test Data Management	Preserving the malformed, historical and hand-fixed records when producing test data - because they are precisely what breaks migrations and new code paths, and a sanitising process removes exactly what made t…
Referentially Consistent Subset Database Subsetting, Coherent Test Slice	practice	Test Data Management	A small extract of a production-shaped database in which every referenced row is present, so a test suite runs against realistic structure at a size that fits an ephemeral per-change environment.
Test Data Management	practice	Test Data Management	The problem of getting data that is realistic enough to find defects and safe enough to exist outside production.
Test Data Provisioning	practice	Test Data Management	Getting each test the data it needs, in a state it can rely on, without copying production personal data into a weaker environment.
Test-Owned Data Data Created By The Test, Per-Test Tenancy	pattern	Test Data Management	Each test creating the exact data it needs through the product's own write path and disposing of it afterwards - replacing shared fixtures whose drift and coupling cause most cross-team test failures.