Terminology

2185 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 areas2185 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture89 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture81 Cost Architecture & FinOps66 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization66 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 concept785 practice729 pattern362 metric125 case-study77 tool62 protocol45

31 terms shown.

Term	Kind	Topic	What it is
Business Capabilities	concept	Business Capabilities	What the business does, expressed independently of how it does it — the most stable frame available for drawing system boundaries.
Business Capability	concept	Business Architecture	What a business does, expressed stably and independently of how it currently does it or who is responsible.
Business Domain Boundary	concept	Domain Boundaries	A division of the business into areas with distinct language, ownership and rates of change, used as the primary input to system and team boundaries.
Business Processes	concept	Business Processes	The sequences of activity that exercise capabilities — where handoffs, exceptions and manual steps reveal what the architecture must support.
Cash-Releasing Benefit Hard Saving, Budget-Line Saving	concept	Business Cases	A benefit that reduces a named budget line on a known date, as distinct from released capacity or avoided cost - which are real but do not become money until a further decision is taken.
Configuration Over Fork Variation as Data, Single Codebase Multi-Market, Parameterised Localisation	concept	Regulatory Constraints	Expressing per-market or per-tenant differences as configuration data and adapters behind stable interfaces rather than as separate codebases, so that improvements ship everywhere and a new market is mostly a …
Cost of Delay	concept	Portfolio Prioritisation	The economic loss per unit of time that a decision or delivery is postponed, which turns prioritisation from opinion into arithmetic.
Exception Tail Long Tail of Cases, Manual Remainder	concept	Business Processes	The minority of cases an automated process cannot handle, whose automation cost per case rises steeply, so the economically correct end state is usually a smaller manual path rather than none.
Flow Efficiency Work-to-Wait Ratio, Process Cycle Efficiency	concept	Value Streams	The proportion of elapsed lead time in which work is actively being done - typically very low, which is why optimising engineering throughput addresses the minority of the problem.
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.
Guarantee Surface Promise Surface, Service Guarantee Footprint	concept	Product Thinking	The set of customer-facing promises a product has made, each of which obliges the architecture to detect its own breach and pay for it - so this surface, not the feature count, drives a whole class of build cost.
Inverted Capability Map System-Derived Capability Model, Inventory-Shaped Capability Map	concept	Capability Mapping	A capability map whose boundaries and names were derived from the existing system inventory, so it confirms the current implementation and cannot show that the business needs something it is not organised to do.
Leading and Lagging Indicator	concept	Business KPIs	The distinction between a measure that predicts an outcome and one that confirms it after the fact, determining whether a metric can be acted on.
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.
Organisational Constraints	concept	Organisational Constraints	The structural, procedural and human limits that determine which designs can actually be built and operated here.
Organisational Readiness	concept	Organisational Constraints	Whether an organisation has the skills, capacity, structure and appetite to operate a proposed architecture, independent of the design's technical merit.
Outcome over Output	concept	Product Thinking	Measuring and committing to changes in user or business behaviour rather than to the delivery of features.
Platform Bypass Signal Adoption as Feedback, Voluntary Platform Use	concept	Platform as a Product	Teams routing around an internal platform read as a product signal about the platform's fitness, not as a compliance failure to be solved with a mandate.
Process Model	concept	Business Processes	A representation of how work actually flows through an organisation, distinguished from a capability by describing sequence, actors and handoffs.
Product Thinking	concept	Product Thinking	Treating what you build as something with users whose problems it must solve — applied to internal platforms as much as to customer-facing products.
Regulatory Constraint	concept	Business Architecture	A legal requirement that removes design options — and one that must be established early, because it is not negotiable and is expensive to retrofit.
Regulatory Constraint as Architectural Driver	concept	Regulatory Constraints	A compliance obligation that removes design options entirely, and therefore belongs among the first constraints identified rather than checked at the end.
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.
Team Interaction Mode	concept	Team Topologies	The defined way two teams work together — collaborating, consuming a service, or facilitating — chosen deliberately and expected to change over time.
Team Topologies	concept	Team Topologies	Four team types and three interaction modes, used deliberately to shape both the organisation and the architecture it produces.
Time to Market	concept	Time to Market	How long from idea to customer value — an architectural property determined by coupling, batch size and the number of teams required.
Two-Pizza Team	concept	Business Architecture	Amazon's heuristic that a team should be small enough to be fed by two pizzas, and — the substantive part — should own its service end to end.
Unfunded Technical Consequence Business-Model Debt, Structural Liability, Implied Requirement	concept	Business Capabilities	A computational or operational difficulty implied by a business-model decision but never costed, because the decision was evaluated on commercial merits in a conversation the technical consequence was not part of.
Value Stream	concept	Business Architecture	The end-to-end sequence of activities that delivers a result to a customer, viewed across whatever departments and systems it happens to cross.
Value Streams	concept	Value Streams	The end-to-end sequence from a customer's trigger to their outcome — the frame that shows whether teams are aligned to flow or to function.