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
8 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. |
| 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. |
| 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. |
| 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. |
| 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.