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

Kind Any concept794 practice734 pattern368 metric125 case-study77 tool62 protocol45

4 terms shown.

Term	Kind	Topic	What it is
Fundable Boundary Budget-Aligned Boundary, Ownable Boundary	concept	Operating Models	A service boundary that sits inside one budget line and one approver - the condition under which it survives contact with the organisation rather than being re-crossed by the first urgent change.
Operating Model	concept	Operating Models	How an organisation arranges people, process, technology and governance to deliver its capabilities, which constrains architecture as strongly as any technical factor.
Operating Models	concept	Operating Models	How an organisation arranges people, ownership and decision rights to deliver and run systems — which determines what architectures are viable.
Shared-Team Queue Central Team Bottleneck, Review Queue	concept	Operating Models	The queueing behaviour of any central team that must approve or perform work for many others, where waiting time rises sharply as utilisation approaches capacity and teams begin routing around the control.