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
Bandwidth-Delay Product	concept	Network Performance	Bandwidth multiplied by round-trip time — the amount of data that must be in flight to keep a link fully utilised.
Connection Fan-In Ephemeral Client Problem, Serverless Connection Storm	concept	Network Performance	The problem created when many short-lived compute instances each require a connection to a stateful dependency that can only support a small number - and the intermediary pattern that resolves it.
ECMP Flow Pinning Flow Hashing, Per-Flow Path Selection	concept	Network Performance	Because a router picks one of several equal-cost paths by hashing a flow's five-tuple, one connection is confined to one link, so aggregate capacity is never per-connection capacity.
Network Performance	concept	Network Performance	Latency is bounded by physics and bandwidth is bought — so architectural performance work is mostly about reducing round trips and moving data closer.