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

5 terms shown.

Term	Kind	Topic	What it is
Hub and Satellite	pattern	Data Vault Modelling	Separating stable business keys from their changing attributes and from their relationships, so each can be loaded independently and kept forever.
Log-Based Ingestion	pattern	CDC Pipeline Design	Building the pipeline around a database's own change log — an initial snapshot followed by a continuous delta stream, with the two stitched together.
Merge Upsert	pattern	Ingestion Patterns	Applying a batch of changes to a target by matching on a key and inserting, updating or deleting per row, which is expensive and frequently avoidable.
Operational Data Push	pattern	Reverse ETL	Sending modelled analytical data back into operational tools, which turns a warehouse table into a production dependency with none of the guarantees.
Query Federation	pattern	Data Virtualisation	Executing a single query across several underlying systems without moving the data, and the performance ceiling that pushdown determines.