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
Fan-Out Delivery	pattern	Publish/Subscribe	Delivering one published message to many independent subscribers, each with its own copy, position and failure handling.
Fan-out Threshold Celebrity Threshold, Hybrid Fan-out Switch	practice	Publish/Subscribe	The membership or follower count at which a system switches from pushing to recipients to having recipients pull - and the monitoring that keeps the classification correct.
Publish-Subscribe Pub/Sub	pattern	Publish/Subscribe	One publication delivered to many subscribers, with the publisher unaware of who they are — and the fan-out problem that comes with it.
Semantic Coupling Meaning Drift, Invisible Event Coupling	concept	Publish/Subscribe	Dependence on what an event or field means rather than on its shape - the coupling that survives every schema check, breaks nothing when violated, and is the hardest failure to detect in an event-driven system.