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

Kind Any concept801 practice736 pattern377 metric127 case-study77 tool62 protocol45

4 terms shown.

Term	Kind	Topic	What it is
Lakehouse Table Format	tool	Open Table Formats	A metadata layer over object storage that adds atomic commits, snapshots and schema evolution to files that otherwise have none.
Open Table Format Iceberg, Delta Lake, Hudi	tool	Open Table Formats	A metadata layer over object storage files that provides atomic commits, schema evolution and time travel, turning a directory of files into a real table.
Transformation Framework ELT Framework, SQL Transformation Tool	tool	Transformation Frameworks	A tool that turns warehouse transformations into version-controlled, tested, dependency-aware code rather than a collection of scheduled scripts.
Workflow Schedulers	tool	Workflow Schedulers	Tools that run interdependent tasks in the right order with retries and visibility — where the value is the explicit dependency graph, not the schedule.