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
6 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Artifact Promotion | practice | Artifact Management | Moving one immutable build between repositories as it earns trust, rather than rebuilding it for each environment. |
| Automated Release Verification | practice | Deployment Gates | A gate that compares the new version's live signals against the old one's and decides, on stated criteria, whether to continue or revert. |
| Configuration Drift Detection | practice | IaC Modules & Drift | Continuously comparing declared infrastructure against what actually exists, so out-of-band change is found on a Tuesday rather than during a rebuild. |
| Forward Fix | practice | Rollback & Forward Fix | Resolving an incident by shipping a correction rather than reverting, which is the right choice exactly when reverting is not actually available. |
| Hermetic Build | practice | Build Reproducibility | A build whose output is a function only of its declared inputs, so the same commit cannot produce two different artifacts. |
| Standard Change | practice | Change Management vs CD | A pre-authorised class of change whose risk controls are automated and evidenced, so it does not need per-instance approval. |
Nothing on this page matches. Search the whole glossary.