Terminology
2240 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 areas2240
Architecture Fundamentals77
Distributed Systems107
Data Architecture110
Cloud Architecture94
Networking88
API & Integration Architecture82
Reliability & Resilience80
Observability75
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 Architecture71
Data Platform Architecture69
Streaming & Real-Time Data69
Data Governance & Semantics74
Frontend & Experience Architecture66
Edge, Mobile & IoT68
Regulatory & Data Protection Architecture65
Assurance, Audit & Model Risk69
71 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Test Pyramid | pattern | Test Pyramid Shapes | The heuristic that a suite should hold many fast isolated tests, fewer integrated ones, and very few full end-to-end tests. |
| Test Quarantine Flaky Test Isolation | practice | Flaky Test Management | Removing an unreliable test from the blocking suite immediately, so it stops eroding trust, while keeping it running non-blocking until it is fixed or deleted. |
| Test Strategy Altitude | concept | Testing & Quality Architecture | Deciding which risks are verified at which level, so that each layer tests something the layers below it structurally cannot. |
| 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. |
| Testability Design for Test | concept | Testing & Quality Architecture | The architectural property that determines what kinds of test are possible - which decides the shape of the suite far more than any testing discipline does. |
| Testability as a Design Property | concept | Test Architecture Strategy | How cheaply a system's behaviour can be observed and controlled, which is decided by architecture and largely fixed before any test is written. |
| Testing in Production TIP | practice | Testing in Production | Deliberately validating behaviour against real traffic, data and scale, using controls that bound the blast radius. |
| Testing Trophy | concept | Test Pyramid Shapes | A distribution weighted towards integration tests rather than unit tests, appropriate where most of the risk lives at boundaries rather than in logic. |
| Traffic Shading Traffic Marking, Shadow Tagging, Request Tainting | pattern | Testing in Production | Marking a request as synthetic and propagating that mark through every hop so downstream services can route its writes to shadow storage and suppress its side effects, which is the single mechanism that makes … |
| Traffic-Mix Skew Canary Population Bias, Assignment Bias | concept | Testing in Production | A canary or experiment arm receiving a population that differs systematically from the baseline - so the comparison measures who was routed rather than what changed. |
| Vacuous Pass Assertion-Free Test, Empty-Set Pass, Silent Test | concept | Testing & Quality Architecture | A test that passes because it verified nothing rather than because the code is correct - an assertion that never ran, a loop over an empty collection, a mock that could not fail - which is worse than having no… |
Nothing on this page matches. Search the whole glossary.