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

27 terms shown.

Term	Kind	Topic	What it is
Accessibility Testing a11y Testing, WCAG Testing	practice	Accessibility Testing	Verifying that an interface is usable by people with disabilities, through automated checks, assistive technology testing and structural review.
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…
Can-I-Deploy Gate Deployment Compatibility Query, Contract Broker Gate	practice	Contract Testing at Scale	A check at deploy time that asks whether this service version is verified against the consumer and provider versions actually running in the target environment - turning contract tests from documentation into …
Chaos Experiment	practice	Chaos as a Test	A controlled fault injected into a system to test a written hypothesis about how it should degrade.
Contract Testing at Scale	practice	Contract Testing at Scale	Operating consumer-driven contracts across hundreds of services, where the broker, versioning and deployment checks become the hard part.
Contract Verification Gate	practice	Contract Testing at Scale	A provider's pipeline stage that replays every consumer's recorded expectations and fails the build if any would break.
Definition of Done	practice	Quality Gates	The agreed, explicit conditions under which work is finished, which functions as a quality gate only when it is automated and non-negotiable.
Deployed-Artefact Assertion Fleet Version Assertion, Release State Check	practice	Testing in Production	A check run after every deployment that compares the build identifier reported by each running host against the intended release, so a partially applied deployment fails loudly instead of running two behaviour…
Deployment Compatibility Check Can-I-Deploy, Deployment Gate on Contracts	practice	Contract Testing at Scale	A pre-deployment query asking whether this version is compatible with everything currently deployed - which turns contract tests from a test into a release gate.
Flake Budget Flakiness Threshold, Quarantine Policy	practice	Flaky Test Management	A hard limit on test flakiness, enforced by automatic detection and quarantine with a deletion deadline - because above a small rate the suite stops being a signal and starts training the team to ignore failures.
Mutation Scope Selection Incremental Mutation Analysis, Diff-Scoped Mutation Testing	practice	Mutation Testing	Restricting mutation analysis to the lines a change touches and to code whose failure is expensive, so a technique that costs one to two orders of magnitude more than the test suite still fits inside a pull-re…
Non-Functional Acceptance	practice	Non-Functional Test Strategy	Treating quality-attribute targets as acceptance criteria with automated verification, so a release can fail on latency the way it fails on a broken feature.
Non-Functional Test Strategy	practice	Non-Functional Test Strategy	The plan for how each quality attribute claim will be demonstrated, tying every NFR to a test that could falsify it.
Performance Test Design	practice	Performance Test Design	Constructing a load test whose result predicts production behaviour rather than merely producing numbers.
Quality and Testing Strategy	practice	Testing & Quality Architecture	How an organisation obtains confidence that changes are safe — a portfolio decision about where to spend limited verification effort.
Quality Gate Threshold	practice	Quality Gates	The specific numeric bar a change must clear, and the perverse incentives it creates when chosen carelessly.
Recorded Interaction Corpus Traffic-Recorded Fixtures, Captured Interaction Set	practice	Service Virtualisation	A set of real request and response pairs captured from a live dependency and used to build and continuously re-verify its stand-in, so the fake reproduces evidence rather than the author's assumptions.
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.
Security Testing in the Pipeline Shift-Left Security, SAST/DAST/SCA	practice	Security Testing in the Pipeline	Automated security analysis embedded in the build, chosen and tuned so that findings are actionable rather than overwhelming.
Shift-Left Security	practice	Security Testing in the Pipeline	Moving security checks earlier so findings arrive while the author still has context, on the condition that the signal-to-noise ratio justifies it.
Side-Effect Isolation Synthetic Traffic Containment, Shadow Write Isolation, Test Traffic Tagging	practice	Testing in Production	Ensuring that test, synthetic or shadowed traffic in production cannot produce real-world effects - the control that separates professional production testing from an incident caused deliberately.
Synthetic Monitoring	practice	Testing in Production	Continuously executing a real user journey against production from outside it, so a broken journey is detected before a user reports it.
Test Architecture Strategy	practice	Test Architecture Strategy	A written decision about which risks are covered by which kind of test, at what scope, run at what point, and which risks are accepted.
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 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.
Testing in Production TIP	practice	Testing in Production	Deliberately validating behaviour against real traffic, data and scale, using controls that bound the blast radius.