Terminology
2205 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 areas2205
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 Architecture69
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 Architecture64
Streaming & Real-Time Data69
Data Governance & Semantics69
Frontend & Experience Architecture66
Edge, Mobile & IoT68
Regulatory & Data Protection Architecture65
Assurance, Audit & Model Risk64
2 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| CI/CD Continuous Integration, Continuous Delivery | practice | CI/CD | Integrating continuously and keeping the software always releasable — a discipline about batch size, with automation as its enabler. |
| Pipeline Feedback Latency Commit-to-Verdict Time, CI Feedback Time | metric | CI/CD | The time from pushing a change to knowing whether it passed, which sets the batch size engineers choose and therefore the size of every review, deploy and rollback. |
Nothing on this page matches. Search the whole glossary.