Portfolio ↗

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

5 terms shown.

Term Kind Topic What it is
Command vs Notification Event Semantics, Obligation vs Fact concept Event-Driven Integration Whether a published message requests an action someone is responsible for, or states a fact the publisher does not care who consumes - and why conflating them causes outages.
Destination Isolation Per-Destination Queues, Independent Fan-Out pattern Event-Driven Integration Fanning events out by writing to a queue per destination rather than delivering synchronously to many, so that one failing or slow destination cannot delay, block or duplicate delivery to the others.
Event Notification vs Event-Carried State concept Event-Driven Integration Whether an event carries only the fact that something happened, or also the data a consumer needs to act on it.
Event Versioning practice Event-Driven Integration Evolving event schemas without breaking consumers that may read messages written months earlier.
Event-Driven Integration pattern Event-Driven Integration Integrating systems by delivering events rather than by polling or synchronous calls — including the delivery guarantees the receiver must be told about.