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

4 terms shown.

Term	Kind	Topic	What it is
Keyed State Size	metric	Stateful Stream Processing	The total state a job holds per key across all keys, which governs memory, checkpoint duration and recovery time.
Rebalance Cost Partition Reassignment Duration, State Restore Time	concept	Stateful Stream Processing	The time a stateful consumer group is unavailable while partitions are reassigned and state restored - proportional to state size, incurred on every deployment, and invisible in throughput and lag metrics.
State Time-to-Live State TTL, State Expiry	practice	Stateful Stream Processing	An expiry policy on stream-processor state so that state size tracks the active key set rather than the accumulated history of everything the job has ever seen.
Stateful Stream Processing	concept	Stateful Stream Processing	Stream computations that must remember information across events — aggregations, joins, deduplication, sessionisation — and the durability machinery that makes them recoverable.