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
Control-Plane Amplification API Server Amplification, Fleet Agent Load Multiplication	concept	Platform Telemetry	The property that a per-instance agent's load on a shared control plane scales with fleet size, so a change that is harmless in staging saturates the API server of the largest production cluster.
Paved Road Telemetry	practice	Platform Telemetry	Instrumenting the platform's own usage — where teams succeed, where they stall, where they leave — so its roadmap is driven by evidence.
Platform Telemetry	practice	Platform Telemetry	Instrumentation of the platform itself — who uses which capability, how long it takes and where it fails — used as product evidence, not just operations.
Usage Telemetry Who Calls This, Consumer Visibility	practice	Platform Telemetry	Per-capability, per-consumer usage data about a platform's own surfaces - the precondition for every deprecation, roadmap and change-impact decision a platform team makes.