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

27 terms shown.

Term	Kind	Topic	What it is
Architectural Drivers	practice	Architectural Drivers	The handful of requirements whose change would force the structure to change — the only ones worth designing against.
Architecturally Significant Requirement ASR	practice	Architectural Drivers	The small subset of requirements whose change would force the structure to change - the only ones an architecture document owes an answer to.
Architecture Documentation	practice	Architecture Documentation	Writing down the decisions and their reasoning at an altitude that stays true long enough to be worth reading.
Architecture Fitness Function in CI Architecture Test, ArchUnit Test	practice	Fitness Functions	An executable check in the build that fails when an architectural constraint is violated, turning a design rule into a property the codebase cannot lose.
Architecture Principle	practice	Architecture Principles	A durable agreed rule that rules options out, stated with rationale and implications rather than as a slogan.
Architecture Principle	practice	Architecture Fundamentals	A durable, agreed rule that constrains design decisions in advance, stated with its rationale and its implications.
Assumption Register	practice	Technical Constraints	The record of the numeric assumptions a design was sized against, monitored so the architecture announces when its own premises expire.
Automated Governance	practice	Fitness Functions	Encoding architectural rules as executable checks in the build pipeline, so conformance is verified continuously rather than reviewed periodically.
Capacity Borrowing Capacity Reallocation, Priority Eviction, Shared Fleet Priority	practice	Architectural Drivers	Serving an unpredictable new load from an existing shared fleet by displacing lower-priority work, which requires that the displaceable work be identified and shaped to be interruptible before the demand arrives.
Change-Reason Cohesion Single Reason to Change, Axis of Change	practice	Cohesion	The working test for a module boundary - things belong together if they change for the same reason, at the same time, driven by the same stakeholder, and share invariants.
Constraint Discovery	practice	Requirements to Constraints	The systematic elicitation of the fixed conditions a solution must satisfy, distinguished from requirements because they are not negotiable and are rarely volunteered.
Constraint Expiry Dated Constraint, Constraint Provenance	practice	Requirements to Constraints	Recording every constraint with its source and its expiry date, so that temporary facts do not get permanently encoded into an architecture.
Counterfactual Structure Test Driver Test, Would-The-Shape-Change Test	practice	Architectural Drivers	The one-question test that separates architectural drivers from important features - remove this requirement, and would the structure of the system change?
Degradation Ladder	practice	Architecture Roles	A pre-agreed ordered list of capabilities the system sheds under load, with the ordering owned by the business and the mechanism owned by the architect.
Evolutionary Architecture	practice	Architecture Fundamentals	Designing for guided, incremental change rather than trying to get the structure right once, up front.
Fitness Function	practice	Architecture Fundamentals	An automated check that an architectural characteristic still holds, run continuously rather than reviewed occasionally.
Inverse Conway Manoeuvre	practice	Conway's Law	Deliberately reorganising teams so that the architecture you want becomes the architecture the organisation naturally produces.
Last Responsible Moment	practice	Evolutionary Architecture	Defer an irreversible decision until the cost of deferring exceeds the cost of deciding - and define in advance the signal that says the moment has arrived.
Non-Functional Budget Quality Attribute Budget, Latency Budget Allocation	practice	Functional vs Non-Functional	Splitting a system-level quality target into per-component allowances with named owners, so a change can be shown to have spent someone's allowance rather than merely argued about.
Principle Rationale	practice	Architecture Principles	The stated reasoning and implications attached to an architecture principle, without which the principle cannot be applied to a case its authors did not foresee.
Principle Statement Format Statement-Rationale-Implication, Testable Principle	practice	Architecture Principles	The four-part shape - statement, rationale, implications, exceptions - that turns an architecture principle from a preference into something that actually rules options out.
Quality Attribute Scenario QA Scenario, Testable NFR	practice	Quality Attributes	A six-part template that turns a vague quality goal into something you can measure and argue about.
Reference Model Tailoring Tailoring Record, Reference Architecture Subsetting	practice	Reference Models	Recording which elements of an adopted reference model you kept, replaced or dropped and why, so a deliberately smaller architecture stays defensible instead of reading as non-compliance.
Replaceability Test Swap Test, Modularity Evidence	practice	Modularity	The evidence-based check for whether a boundary is real - not how many services exist, but whether one implementation could be swapped without touching the others, and whether it ever has been.
Requirements to Constraints	practice	Requirements to Constraints	The translation step where a stated business wish becomes a number that rules designs out.
Rule of Three Abstract at the Third Instance, Duplicate Before Abstracting	practice	Evolutionary Architecture	Hard-code the first case, copy for the second, abstract at the third - because only the third instance reveals which parts actually vary.
Utility Tree	practice	Quality Attributes	A structured decomposition of quality attributes into concrete, prioritised scenarios, used to focus architectural analysis on what actually matters.