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
Explained-Difference Criterion Shadow Exit Criterion, Zero Unexplained Differences	practice	Parallel Run	Ending a shadow or parallel run when every observed difference has been explained, rather than when differences reach zero - because zero is unachievable and unexplained differences are by definition the dange…
Parallel Run	practice	Parallel Run	Operating the old and new systems simultaneously on the same inputs and comparing outputs, to build evidence that the replacement is correct before relying on it.
Shadow Comparison	pattern	Parallel Run	Running a new implementation alongside the old on real traffic, comparing outputs without the new system affecting users.
Traffic Shadowing Dark Traffic, Mirroring, Shadow Testing	pattern	Parallel Run	Sending a copy of real production traffic to a new implementation while the existing one continues to serve users, comparing results without exposing anyone to the new system's mistakes.