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

21 terms shown.

Term	Kind	Topic	What it is
Anaemic Domain Model	concept	Domain-Driven Design	Objects that hold data with no behaviour, leaving business rules scattered across service classes where they are duplicated and inconsistently applied.
Architectural Significance Architecturally Significant Decision, Significance Test	concept	Software Architecture	The test that separates decisions worth reviewing from the ones a team should make alone, by asking what undoing each one would cost rather than how technical it sounds.
Boundary Reversal Asymmetry Split Reversal Cost, Asymmetric Boundary Error	concept	Service Boundaries	The fact that a boundary drawn too coarse is cheap to split later while one drawn too fine is expensive to merge, which makes the coarse error the right default when evidence is thin.
Bounded Context	concept	Bounded Contexts	A boundary within which a model and its vocabulary are internally consistent, and outside which the same words may legitimately mean something different.
Debt Interest Rate Cost Per Unit Time, Debt Triage Axis	concept	Technical Debt	How much a piece of technical debt costs per unit time in slowed delivery, incidents and effort - which, paired with the cost to fix, is what separates debt worth paying down from debt that merely looks unpleasant.
Dependency Inversion	concept	SOLID	The rule that high-level policy should not depend on low-level detail, both depending instead on an abstraction owned by the policy.
Dependency Rule	concept	Clean Architecture	The constraint that source-code dependencies may point only inward, from detail toward policy, regardless of the direction of control flow.
Design Patterns	concept	Design Patterns	Named solutions to recurring design problems — valuable primarily as shared vocabulary, and harmful when applied as a goal.
Distributed Monolith	concept	Microservices	A system split into services that must still be deployed, changed and operated together, incurring distribution costs without independence.
Flag Debt	concept	Feature Flags	The accumulating complexity of feature flags that are never removed, producing untested code paths and combinatorial behaviour nobody understands.
Independent Deployability	concept	Microservices	The property that a service can be released to production without coordinated release of any other, which is the defining benefit of microservices.
Invariant Containment Boundary Follows the Invariant, Transaction Test	concept	Service Boundaries	The rule that a service boundary must contain any invariant that must hold exactly - so discovering that a split would break a transaction is evidence the boundary is wrong, not merely an obstacle.
Module Public Surface Module Exported Surface, Module Entry Points	concept	Modular Monolith	The set of types a module lets other modules reach, which decides how much of it can be rewritten or extracted without touching anyone else's code.
Pattern Overuse	concept	Design Patterns	Applying a design pattern where the problem it solves does not exist, adding indirection and vocabulary without benefit.
Service Boundary	concept	Software Architecture	The line separating what one service owns and is accountable for from what it must ask another service about.
SOLID Principles	concept	SOLID	Five object-design principles whose architectural value lies almost entirely in the last one — dependency inversion.
Speculative Abstraction Premature Abstraction, Anticipatory Design	concept	Design Patterns	Structure added for variation that has not occurred - paying certain indirection now for a benefit that depends on a guess about the future.
Suite Reliability Arithmetic Per-Test Flake Rate Derivation, Suite Green-Rate Calculation	concept	Testing Strategies	The calculation that turns a suite's target green rate and its test count into the per-test flake rate each test must meet, which is what determines how many high-level tests a team can afford to have at all.
Technical Debt	concept	Software Architecture	The future cost incurred by choosing an expedient implementation now instead of the better one.
Technical Debt Quadrants	concept	Technical Debt	Distinguishing debt by whether it was taken deliberately or inadvertently, and prudently or recklessly, since the four kinds need different responses.
Testing Strategy Shape	concept	Testing Strategies	The distribution of tests across levels, chosen so that feedback is fast where it can be and confidence is real where it must be.