Terminology

2240 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 areas2240 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture94 Networking88 API & Integration Architecture82 Reliability & Resilience80 Observability75 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 Architecture71 Data Platform Architecture69 Streaming & Real-Time Data69 Data Governance & Semantics74 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk69

Kind Any concept806 practice738 pattern379 metric133 case-study77 tool62 protocol45

4 terms shown.

Term	Kind	Topic	What it is
Data Virtualisation Query Federation, Logical Data Warehouse	pattern	Data Virtualisation	Querying data where it lives across multiple systems through a single logical layer, without physically consolidating it.
Predicate Pushdown Filter Pushdown, Pushdown Optimisation	concept	Data Virtualisation	Sending a filter to the layer that holds the data rather than fetching rows and filtering afterwards, which is the difference between reading megabytes and reading a table.
Query Federation	pattern	Data Virtualisation	Executing a single query across several underlying systems without moving the data, and the performance ceiling that pushdown determines.
Source Load Budget Upstream Read Quota, Analytical Load Cap	pattern	Data Virtualisation	An explicit cap on the concurrency, rows and duration that analytical reads may consume on an operational source - so a dashboard query cannot become a production incident.