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
70 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Structured Logging | practice | Structured Logging | Emitting logs as machine-parseable key-value records rather than formatted prose, so they can be queried, aggregated and correlated. |
| Symptom-Based Alerting Alert on Effects, User-Visible Alerting | concept | Alert Fatigue | Paging on what the user experiences and investigating causes with dashboards - because cause-based alerts fire in clusters during a single incident and bury the signal they exist to provide. |
| Tail-Based Sampling Post-Trace Sampling, Intelligent Sampling | practice | Sampling | Deciding whether to keep a trace after it completes, so that errors and slow requests are always retained while ordinary traffic is sampled cheaply. |
| Telemetry Cost Control | practice | Telemetry Cost | Managing the spend on logs, metrics and traces, which in mature estates can approach or exceed the cost of the infrastructure being observed. |
| Telemetry Cost Management | practice | Telemetry Cost | Controlling observability spend through sampling, retention tiering and cardinality limits without losing diagnostic capability. |
| Telemetry Pipeline Lag Ingestion Delay, Time to Queryable, Observability Freshness | metric | Observability | The delay between an event being emitted and being queryable, which bounds how quickly any decision made from telemetry can respond to reality. |
| Telemetry Sampling | practice | Observability | Keeping a subset of traces or events to bound observability cost, chosen so the ones that matter survive. |
| Trace Sampling Strategy Head Sampling, Tail Sampling | practice | Sampling | Deciding which traces to keep, since retaining all of them at scale is unaffordable and retaining a random few loses exactly the interesting ones. |
| USE Method | practice | Observability | For every resource, track Utilisation, Saturation and Errors — the resource-centric complement to request-centric monitoring. |
| 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… |
Nothing on this page matches. Search the whole glossary.