THE CORE AIM OF VOCABULARY MASTERY · DATA ARCHITECTURE VOCABULARY · SOURCE → FLOW → STORE → MODEL → GOVERN
Data architecture vocabulary is the language used to describe how an organisation’s data sources, stores, pipelines, models and governance controls fit together. Terms such as source system, data domain, data platform, integration, warehouse, lake, semantic layer, lineage and reference architecture matter because architecture is about the relationships among systems, not one database in isolation.
The core aim of vocabulary mastery for data architecture vocabulary is system-level data clarity. Learners should be able to explain where data originates, how it moves, where it is stored, how it is modelled, which teams own it and what architectural trade-offs shape reliability, access and cost.
This page is the Data Architecture Vocabulary owner inside the eduKateSG Vocabulary hub. For logical structures, use Data Modeling Vocabulary. For pipelines, use Data Engineering Vocabulary.
Central proposition: Data architecture vocabulary is mastered when the learner can see the whole data landscape as connected sources, flows, stores, models and governance boundaries.
The 60-Second Data Architecture Vocabulary Router
- Source: source system, domain, producer, event.
- Flow: pipeline, integration, batch, stream, replication.
- Store: operational database, warehouse, lake, lakehouse.
- Model: schema, semantic layer, canonical model.
- Govern: owner, lineage, policy, classification.
- Design: reference architecture, pattern, boundary, trade-off.
The Data Architecture Vocabulary Architecture
| Layer | Core terms | Core question |
|---|---|---|
| Source | system, domain, producer | Where does data originate? |
| Movement | pipeline, stream, replication | How does it travel? |
| Storage | database, warehouse, lake | Where is it kept? |
| Model | schema, semantic layer | How is meaning organised? |
| Governance | owner, lineage, policy | Who controls and explains it? |
| Architecture | pattern, boundary, trade-off | How do the parts fit together? |
Data Architecture and Data Modeling Are Different
Data modeling focuses on the internal structure of entities, relationships, facts and dimensions. Data architecture operates at a wider system level: sources, platforms, pipelines, stores, ownership and integration patterns.
A Worked Example: Source System
A source system is an operational system where data originates, such as an order platform, CRM or sensor network. Architecture vocabulary asks how that source publishes data, who owns it and what downstream systems depend on it.
A Worked Example: Semantic Layer
A semantic layer gives business-friendly meaning to underlying data by defining reusable metrics, relationships and concepts. It helps multiple reports use the same definitions instead of creating competing versions of revenue, customer or conversion.
Reference Architecture and Pattern
A reference architecture is a reusable high-level blueprint for a class of systems. An architectural pattern is a repeatable design approach to a common problem. Both guide design without replacing local constraints and decisions.
Architecture and Trade-Offs
Data architecture vocabulary includes latency, cost, consistency, availability, scalability and governance because no design optimises every quality equally. Architecture is the art of making those trade-offs visible.
How to Learn Data Architecture Vocabulary
- Draw an end-to-end data landscape.
- Label producers, stores and consumers.
- Trace one critical dataset across systems.
- Identify ownership and governance boundaries.
- Compare batch, streaming and replication patterns.
- Connect design choices to latency, cost and reliability.
- Explain the architecture to both technical and business audiences.
Common Data Architecture Vocabulary Mistakes
Confusing architecture with schema design
Repair: widen the view to systems, flows and governance.
Drawing boxes without ownership
Repair: identify who operates and governs each data domain.
Ignoring consumers
Repair: trace architecture through to reports, applications and decisions.
Using patterns without trade-off language
Repair: state why the pattern fits the workload and what it costs.
Frequently Asked Questions
What is data architecture vocabulary?
It is the language used to describe data sources, platforms, pipelines, storage, models, governance and system-wide design patterns.
What terms should beginners learn first?
Start with source system, pipeline, warehouse, data lake, semantic layer, lineage, domain and reference architecture.
How is data architecture different from data modeling?
Data modeling focuses on structure inside datasets; architecture focuses on the wider ecosystem of systems and flows.
What is a semantic layer?
It is a shared business-meaning layer that defines reusable concepts and metrics over underlying data.
How can I learn data architecture vocabulary?
Map one organisation’s data landscape and trace one dataset from source through storage and transformation to its consumers.
Where This Article Fits in the eduKateSG Vocabulary Ecosystem
- Vocabulary Hub — the broad route.
- Data Modeling Vocabulary — internal data structure.
- Data Engineering Vocabulary — pipelines.
- Data Governance Vocabulary — ownership and policy.
- Data Warehousing Vocabulary — analytical storage.
The Data Architecture Vocabulary Standard
Data architecture vocabulary reaches its core aim when the learner can explain where data comes from, how it moves, where it lives, how meaning is defined and who is accountable for it.
That is the standard: system-level data language that makes the whole landscape visible.