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
3 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Boundary Volatility Test | practice | Service Boundaries | Evaluating a proposed service boundary by asking whether the things on either side change for different reasons and at different rates. |
| Co-Change Analysis Change Coupling, Logical Coupling | practice | Service Boundaries | Using version-control history to find which components change together - the strongest available evidence that a proposed boundary is right or wrong. |
| Service Boundary Heuristics | practice | Service Boundaries | The signals that indicate where a service boundary belongs, and the ones that reliably mislead. |
Nothing on this page matches. Search the whole glossary.