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
Deployability Test Can You Deploy Alone, Boundary Justification Test	practice	Microservices	Asking whether one team can change, deploy and roll back a service without telling the others - the single test that distinguishes a boundary delivering independence from one delivering only cost.
Distributed Monolith	concept	Microservices	A system split into services that must still be deployed, changed and operated together, incurring distribution costs without independence.
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.
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.