Terminology

454 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 areas454 Architecture Fundamentals16 Distributed Systems73 Data Architecture71 Cloud Architecture55 Networking13 API & Integration Architecture17 Reliability & Resilience16 Observability14 Performance & Capacity Engineering13 Security Architecture50 Cost Architecture & FinOps12 Business Architecture9 Architecture Communication8 Enterprise Architecture8 Legacy Modernization11 AI-Era Architecture15 Software Architecture & Engineering19 Architecture Patterns15 Architecture Decision-Making11 The Architect's Meta-Skills8

Kind Any concept166 practice107 pattern93 case-study26 tool26 protocol22 metric14

6 terms shown.

Term	Kind	Topic	What it is
Architecture Cost Model	practice	Cost & FinOps	A calculation, made during design, of what an architecture will cost to run at expected and at peak volume.
Chargeback and Showback	practice	Cost & FinOps	Attributing cloud cost to the teams that generate it — either informationally (showback) or by moving it onto their budget (chargeback).
Egress Path Analysis	practice	Network & Egress Costs	Tracing where data physically moves in an architecture, because transfer charges follow paths that appear nowhere on the diagram.
FinOps	practice	Cost & FinOps	The practice of giving engineering teams visibility into and accountability for the cost of what they build and run.
Rightsizing	practice	Cost & FinOps	Matching provisioned resources to observed demand, rather than to the guess made when they were created.
Storage Tiering	practice	Cost & FinOps	Moving data between access tiers as it cools, so rarely-read data is not paying hot-storage prices.