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
Blue-Green Deployment	pattern	Deployment Strategies	Two complete production environments where traffic is switched from the old to the new in one step, and back just as fast.
Leading Health Signal In-Band Invariant Signal, Detection-Latency Gate	concept	Deployment Strategies	A rollout gate input whose latency is shorter than the damage it indicates - the property that decides whether any bake time can catch a defect, as distinct from how much traffic the rollout exposes.
Release Train	pattern	Deployment Strategies	A fixed-cadence release where whatever is ready by the departure time ships, and whatever is not waits for the next one.
Rolling Update Surge	concept	Deployment Strategies	The extra capacity a rolling deployment temporarily adds, and the unavailability it is permitted, which together decide whether the rollout is safe under load.