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

794 terms shown.

Term	Kind	Topic	What it is
Wide Event Canonical Log Line, Arbitrarily-Wide Structured Event, Unit-of-Work Event	concept	Observability	A single structured record per unit of work carrying every field that might matter, aggregated only at query time - so questions nobody anticipated remain answerable, which pre-aggregated metrics make permanen…
Windowing	concept	Streaming Data	Grouping an unbounded stream into finite chunks so aggregation can produce results, defined over event time rather than arrival time.
Windowing Strategy	concept	Windowing	The choice of how a continuous stream is divided into finite groups for aggregation, which determines both the meaning of the result and the state it requires.
Working Set Hot Data Set	concept	Caching for Performance	The subset of data actually touched in a given window, whose size against the cache's capacity determines the hit rate and therefore how much load reaches the origin.
Workload Identity SPIFFE, Managed Identity, Service Identity	concept	Identity & Access Management	Giving a running workload a cryptographic identity derived from its platform context, so it can authenticate without a stored credential.
Write Amplification	concept	Partitioning & Sharding	One logical write producing many physical writes - through fan-out, indexes, replication or storage-engine mechanics - and why it decides scaling limits.
Write Contention Row Contention, Hot Row	concept	Performance & Capacity	Many concurrent writers competing for the same item of state, which serialises through one lock and cannot be relieved by adding capacity.
Write Skew	concept	Transactions & Isolation	An anomaly where two transactions each read a set of rows, make disjoint writes based on what they read, and together violate an invariant neither could have broken alone.
Write-Ahead Log WAL, Commit Log	concept	Data Architecture	Recording every change to a durable sequential log before applying it, so that a crash can be recovered by replaying the log.
X-Forwarded-For Forwarded Header	concept	Reverse Proxies	The header chain recording original client addresses through a series of proxies — and a value that must never be trusted without knowing the topology.
Zero Trust	concept	Security Architecture	A security model that grants no implicit trust from network position, and authenticates and authorises every request individually.
Zombie Integration Orphaned Interface, Decommissioning Debris	concept	Application Rationalisation	An interface left running after the system at one end is retired - it consumes credentials and produces stale or lost data, prevents the savings from being booked, and makes the surrounding estate harder to change.
Zombie Task Orphaned Task, Heartbeat-Expired Task	concept	Batch Orchestration	A task whose worker has stopped reporting to the scheduler but whose process may still be running and writing, so the orchestrator retries work that has not actually stopped.
Zonal vs Regional Services	concept	Availability Zones	Whether a cloud resource lives in one availability zone or is inherently spread across several — a property that determines what a zone failure takes with it.