Terminology

991 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 areas991 Architecture Fundamentals38 Distributed Systems73 Data Architecture71 Cloud Architecture55 Networking51 API & Integration Architecture45 Reliability & Resilience40 Observability33 Performance & Capacity Engineering34 Security Architecture50 Cost Architecture & FinOps30 Business Architecture28 Architecture Communication27 Enterprise Architecture27 Legacy Modernization27 AI-Era Architecture34 Software Architecture & Engineering37 Architecture Patterns34 Architecture Decision-Making30 The Architect's Meta-Skills27 Delivery & Release Engineering20 Platform Engineering & Developer Experience20 Testing & Quality Architecture20 Data Platform Architecture20 Streaming & Real-Time Data20 Data Governance & Semantics20 Frontend & Experience Architecture20 Edge, Mobile & IoT20 Regulatory & Data Protection Architecture20 Assurance, Audit & Model Risk20

Kind Any concept379 practice294 pattern166 metric55 tool36 protocol35 case-study26

7 terms shown.

Term	Kind	Topic	What it is
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.
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.
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.
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 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	practice	Flaky Test Management	Moving an intermittently failing test out of the blocking suite into a tracked, owned backlog, so a red build keeps meaning something.