Terminology

2225 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 areas2225 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 Architecture74 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 Architecture69 Streaming & Real-Time Data69 Data Governance & Semantics74 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk69

Kind Any concept801 practice736 pattern377 metric127 case-study77 tool62 protocol45

4 terms shown.

Term	Kind	Topic	What it is
Denormalised Log Resolved-Asset Topic, Fat Event Stream	pattern	Kappa vs Lambda	A second topic that republishes each record with its referenced data already resolved, so consumers read complete payloads instead of each performing the same joins against the normalised source of truth.
Kappa Architecture	pattern	Kappa vs Lambda	Treating the stream as the single processing path, and handling historical reprocessing by replaying the log through the same code.
Lambda Architecture Batch and Speed Layer, Dual-Path Analytics	pattern	Kappa vs Lambda	Running the same computation as both a scheduled recomputation over all retained history and a streaming job over recent events, so that any defect in the fast path is erased by the next full recomputation.
Replay Pipeline	pattern	Kappa vs Lambda	A single processing path that produces both live and historical results by re-running the same code over retained input, replacing the two-path Lambda arrangement.