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

3 terms shown.

Term	Kind	Topic	What it is
Business Continuity	practice	Business Continuity	Keeping the business operating through disruption — a broader discipline than disaster recovery, and one that includes not using the system at all.
Business Impact Analysis	practice	Business Continuity	Determining which business processes must be restored, how quickly, and what the consequence of not doing so is — the input from which recovery targets are derived.
Manual Fallback Capacity Degraded-Mode Throughput, Paper-Process Capacity	practice	Business Continuity	The transactions per hour a business can actually complete without its system - the measured number that says whether a recovery-time objective is survivable and how long the catch-up takes.