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 |
|---|---|---|---|
| Amazon Prime Video: Serverless Back to a Monolith Prime Video Audio/Video Monitoring | case-study | Monolith vs Microservices | A distributed serverless pipeline was consolidated into a single process, reducing cost by over 90% — for one component, for specific reasons that do not generalise. |
| Extraction Payback Period | metric | Monolith vs Microservices | The time it takes for the coordination cost a service extraction removes to repay the one-off extraction cost plus the permanent cost of running one more deployable - which is usually never unless the module h… |
Nothing on this page matches. Search the whole glossary.