Terminology

2185 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 areas2185 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture89 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture81 Cost Architecture & FinOps66 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization66 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 concept785 practice729 pattern362 metric125 case-study77 tool62 protocol45

17 terms shown.

Term	Kind	Topic	What it is
Architecture Sinkhole	concept	Layered Architecture	A request that passes through every layer of a layered architecture without any layer adding logic, indicating that the layering is pure overhead for that path.
Choreography vs Orchestration	concept	Orchestration vs Choreography	Whether a multi-service process is driven by a central coordinator or emerges from services reacting to each other's events.
Consumer Liveness Gap Zombie Consumer, Progress Blindness	concept	Competing Consumers	The interval in which a queue consumer is alive by every health signal yet is making no progress, so its share of the work stalls while pool-level metrics stay normal.
Contract Event Designed Event vs Row Change, Deliberate Emission	concept	Outbox	An event a system deliberately emits with a schema it owns and a meaning it controls, as opposed to a captured row change that exposes the producer's table structure as a public interface.
Control-Plane Push Amplification Config Fan-Out, xDS Amplification	concept	Service Mesh	The property that one endpoint change can force a configuration push to every proxy in the fleet, making control-plane work scale with proxies multiplied by services rather than with either alone.
Filter Composability	concept	Pipes and Filters	The property that makes a pipeline style work — each stage transforms input to output with no shared state, so stages can be reordered, reused and scaled independently.
Mesh Control Plane	concept	Service Mesh	The component that configures and coordinates a service mesh's data plane proxies, distributing policy, identity and routing rules.
Partition Assignment	concept	Competing Consumers	The mapping of partitions to consumer instances that determines parallelism, ordering guarantees and what happens when the consumer set changes.
Process Ownership Gap Unowned Workflow, Orphaned Business Process	concept	Orchestration vs Choreography	The condition in which every step of a multi-service process has an owning team but the process itself has none, so a stall produces no error, no deadline breach and no page.
Replay Determinism Projection Purity, Deterministic Fold	concept	Event Sourcing	The property that folding an event log through a projection handler yields the same state every time it is run, which is what makes an event log rebuildable rather than merely stored.
Saga Isolation Anomaly	concept	Saga	The intermediate states visible to other transactions during a saga, because a saga provides atomicity and durability but not isolation.
Selective Reliability Partial Reliability, Deadline-Aware Delivery	concept	Pipes and Filters	Retransmitting only what is still useful and discarding what has expired - because for time-sensitive data, late delivery consumes capacity without providing value.
Semantic Coupling Meaning Drift, Invisible Event Coupling	concept	Publish/Subscribe	Dependence on what an event or field means rather than on its shape - the coupling that survives every schema check, breaks nothing when violated, and is the hardest failure to detect in an event-driven system.
Sidecar Interception Boundary Mesh Coverage Boundary, Proxy Capture Scope	concept	Sidecar & Ambassador	The precise set of traffic a sidecar proxy actually sees and can secure, which is narrower than "all traffic from this pod" and is what decides whether a mesh's guarantees apply to a given call.
Sidecar Resource Overhead	concept	Sidecar & Ambassador	The cumulative CPU, memory and latency cost of running helper containers alongside every application container.
View Staleness Window	concept	Materialized Views	The maximum age of data in a precomputed view, which must be an explicit, monitored contract rather than an incidental property.
Visibility Timeout Message Lease, Invisibility Window	concept	Competing Consumers	The period a claimed message is hidden from other consumers - too short and work is duplicated, too long and a crashed worker stalls the item.