Terminology

2225 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 areas2225 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 Architecture74 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 Architecture69 Streaming & Real-Time Data69 Data Governance & Semantics74 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk69

Kind Any concept801 practice736 pattern377 metric127 case-study77 tool62 protocol45

71 terms shown.

Term	Kind	Topic	What it is
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.
Sync Engine Local-First Sync, Client Database Replication, Delta Sync	pattern	Modular Monolith	A client-side database kept continuously in sync with the server through deltas, so every read and write is local and instantaneous - moving the network off the interaction critical path entirely.
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 Strategies	practice	Testing Strategies	Choosing what to test at which level, optimising for confidence per unit of time and maintenance rather than for coverage.
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.
Trunk-Based Development in Practice	practice	Trunk-Based Development	Everyone integrates to one shared branch at least daily, with incomplete work hidden behind flags rather than isolated in branches.
Uber DOMA: Structure Above Microservices Domain-Oriented Microservice Architecture	case-study	Microservices	Having reached thousands of microservices, Uber introduced domains and layers above them because independent services had recreated the coordination problem they were meant to solve.
Uber's Domain-Oriented Microservice Architecture DOMA	case-study	Software Architecture	After growing to roughly 2,200 microservices, Uber grouped them into domains behind gateways with strict dependency layering, to recover the comprehensibility that fine-grained decomposition had cost.
Ubiquitous Language	practice	Domain-Driven Design	A shared vocabulary used identically by domain experts and in the code, so that translation between business and implementation is unnecessary.