Terminology

2240 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 areas2240 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture94 Networking88 API & Integration Architecture82 Reliability & Resilience80 Observability75 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 Architecture71 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 concept806 practice738 pattern379 metric133 case-study77 tool62 protocol45

3 terms shown.

Term	Kind	Topic	What it is
Freshness Requirement	concept	Streaming vs Batch	How stale data may be before the decision it supports degrades — the only question that justifies streaming over batch.
Micro-Batching Mini-Batch Streaming, Discretised Stream Processing	pattern	Streaming vs Batch	Executing a stream as a sequence of small bounded jobs on a fixed trigger interval, which buys batch failure semantics and atomic sink commits at the price of a latency floor equal to the interval.
Streaming vs Batch Decision	practice	Streaming vs Batch	Choosing between continuous and periodic processing based on the decision latency the business actually requires, not on the appeal of real-time.