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
20 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Certified Report | practice | BI Governance | A small set of reports explicitly endorsed as authoritative, with an owner and a review cadence, distinguished from everything else people have built. |
| Code List Governance | practice | Reference Data | Managing the small shared enumerations — currencies, country codes, statuses, product categories — whose uncontrolled change breaks systems quietly. |
| Computation-Only Collaboration | pattern | Data Sharing & Clean Rooms | Two parties analysing their combined data without either receiving the other's records, by permitting only queries whose outputs are aggregate. |
| Data Product Interface | concept | Data Products | The stable surface a data product exposes — its schema, its access path, its documentation and its guarantees — as distinct from the pipeline behind it. |
| Decision Rights Over Data | concept | Data Governance & Semantics | Who is entitled to decide what a data element means, who may see it and how long it is kept — the substance of governance once the policy documents are set aside. |
| Deletion Verification | practice | Retention & Purge | Proving that a deletion actually removed the data everywhere it existed, which is a harder problem than issuing the delete. |
| Deterministic Tokenisation | practice | Tokenisation & Masking | Replacing a sensitive value with a stable surrogate so the same input always yields the same token, preserving joins while removing the value. |
| Domain Data Ownership | concept | Data Mesh | Making the team that generates data accountable for publishing it fit for others to use, rather than handing raw extracts to a central team. |
| Golden Record | concept | Master Data Management | The single authoritative version of an entity assembled from conflicting sources, and the survivorship rules that decide which value wins. |
| Governed Self-Service | concept | Self-Service vs Governed | Letting anyone analyse anything while constraining what may be treated as authoritative, which resolves the apparent conflict between speed and consistency. |
| Metadata Harvesting | practice | Data Catalog | Populating a catalogue automatically from the systems that hold the data, because anything requiring manual entry will be incomplete within a quarter. |
| Metric Definition Layer | pattern | Semantic Layer | Business metrics defined once in a versioned, tested place and served to every consuming tool, so the number cannot differ by which tool asked. |
| Pipeline Anomaly Detection | practice | Data Observability | Monitoring row counts, distributions, freshness and schema for unexplained change, because data pipelines fail silently far more often than they error. |
| Predicate-Based Filtering | pattern | Row & Column-Level Security | A policy that appends a filter to every query on a table based on who is asking, so one physical table serves many audiences safely. |
| Producer Obligation | concept | Data Contracts | What a data contract binds the producing team to do, and — crucially — what happens in their pipeline when they are about to break it. |
| Purpose-Based Access | pattern | Data Access Models | Granting access for a stated and recorded purpose rather than by role alone, which is what several data protection regimes actually require. |
| Quality Dimension Threshold | metric | Data Quality Dimensions | The stated numeric level at which a dataset is fit for its purpose on a given quality dimension, plus what happens when it is not met. |
| Sensitivity Propagation | concept | Sensitivity Labelling | The rule that a derived dataset inherits the highest sensitivity of its inputs unless a named transformation demonstrably lowers it. |
| Steward Accountability | practice | Data Stewardship | Making stewardship a defined role with time, authority and consequences, rather than a title added to somebody's existing job. |
| Term Definition Ownership | practice | Business Glossary | Assigning one accountable owner per business term, so that a disagreement about meaning has a route to resolution rather than a standing argument. |
Nothing on this page matches. Search the whole glossary.