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
3 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Build Attestation | concept | Supply-Chain Provenance | A signed statement about how an artifact was produced — by which builder from which source — that a deployment gate can verify rather than trust. |
| Release Tarball Divergence Archive-Repository Gap, Distributed-Source Divergence | concept | Supply-Chain Provenance | The gap between a project's reviewed source repository and the source archive that downstream actually builds, which is a trust boundary most supply-chain controls assume does not exist. |
| Software Bill of Materials SBOM | tool | Supply-Chain Provenance | A machine-readable inventory of every component and dependency inside a built artifact. |
Nothing on this page matches. Search the whole glossary.