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

20 terms shown.

Term	Kind	Topic	What it is
Consent Propagation	concept	Consent Architecture	Ensuring a consent decision reaches and is honoured by every system that processes the data, including those that received it before the decision changed.
Data Minimisation	concept	Privacy by Design	Collecting and retaining only what a stated purpose requires, which reduces both regulatory exposure and breach impact at the same time.
Differential Privacy Budget	concept	Privacy-Enhancing Technologies	The cumulative privacy loss permitted across all queries against a dataset, which must be tracked and exhausted rather than applied per query.
Fourth Party Risk	concept	Third-Party Risk	The dependencies of your dependencies, which you did not choose, may not know about, and remain accountable for.
Geo-Blocking Accuracy	concept	Geo-Restriction & Sanctions	The reliability of determining a user's jurisdiction from network signals, which is imperfect in both directions and therefore needs a designed handling of errors.
Immutable Store Erasure Conflict	concept	Erasure vs Immutability	The direct contradiction between architectures designed never to forget and obligations requiring data to be removed, which must be resolved in the design rather than in policy.
In-Country Processing	concept	Data Residency	Keeping data within a jurisdiction across every path it takes — including backups, logs, telemetry, support access and the disaster recovery region.
Legal Hold	practice	Records Retention & Legal Hold	Suspending deletion for specific records because of anticipated litigation or investigation, which must override the retention schedule and be provable.
Material Outsourcing Notification	practice	Sector Cloud Rules	The regulatory obligation to inform a supervisor before placing a critical function with a third party, which puts cloud adoption on a timeline architecture must respect.
Minimum Necessary Access	concept	Healthcare Data Protection	Restricting each user to the health information required for their specific role and, in the strong form, to the patients they are actually treating.
Obligation Mapping	practice	Regulatory & Data Protection Architecture	Translating each legal or regulatory requirement into the specific design constraints it imposes, so that compliance becomes a set of testable properties rather than a document.
Operational Resilience Requirement	concept	Financial Services Regulation	A supervisory expectation that a firm can continue delivering critical business services through disruption, expressed as an impact tolerance it must evidence.
Operator Independence	concept	Digital Sovereignty	The requirement that no foreign entity can be compelled to access or disclose data, which goes beyond where the bytes are stored to who controls the operator.
Provider Exit Plan	practice	Exit & Concentration Risk	A documented and tested plan for moving a workload off a provider, whose credibility is measured by what has actually been rehearsed rather than described.
Purpose Binding	concept	Lawful Basis & Purpose Limitation	Attaching the reason data was collected to the data itself, so a later use that does not match can be identified rather than assumed permissible.
Re-Identification Risk	concept	Pseudonymisation	The probability that pseudonymised data can be linked back to individuals, which is what keeps such data within the scope of data protection law.
Scope Reduction	practice	PCI-DSS Scoping	Shrinking the set of systems that store, process or transmit cardholder data, because the cost of the standard is proportional to the number of systems in scope.
Subject Access Fulfilment	practice	Data Subject Rights	The operational path from a request to a complete, verified, delivered response within the statutory period, across systems that were never designed for it.
Submission Deadline Architecture	concept	Regulatory Reporting Pipelines	Designing a reporting pipeline around a fixed external deadline, where late is a breach and the recovery window is part of the schedule rather than a contingency.
Transfer Mechanism	concept	Cross-Border Transfer	The specific legal instrument permitting personal data to leave a jurisdiction, which must exist per flow and which architecture must make identifiable.