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
5 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| 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. |
| Master Data Management MDM, Golden Record | practice | Master Data Management | Establishing a single authoritative version of core business entities that appear inconsistently across many systems. |
| Match Confidence Band Match Threshold Band, Review Band | metric | Master Data Management | The score range between automatic merge and automatic reject in record matching, which is where a consolidation programme's permanent staffing cost lives and where its worst errors are prevented. |
| Survivorship Rules Golden Record Rules, Attribute Precedence | practice | Master Data Management | Per-attribute rules deciding which source's value wins when several systems hold a different value for the same entity - the part of master data management that determines whether the golden record is trusted. |
| Unmerge Capability Merge Reversal, Split-Back | pattern | Master Data Management | The designed ability to reverse an incorrect entity merge and restore both original records, which requires that source keys and pre-merge attribute values were never destroyed. |
Nothing on this page matches. Search the whole glossary.