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

7 terms shown.

Term	Kind	Topic	What it is
Burn Rate Alerting Multi-Window Multi-Burn-Rate, SLO Burn Alert, Budget Consumption Alert	pattern	Alerting	Alerting on how fast an error budget is being consumed, across multiple time windows simultaneously, so that a sudden outage pages immediately while a slow erosion opens a ticket.
Context Propagation	pattern	Correlation IDs	Carrying request-scoped identifiers and metadata across every service, thread and asynchronous boundary so a single flow remains traceable end to end.
Correlation IDs Request ID, Trace ID	pattern	Correlation IDs	A single identifier attached at the edge and carried through every hop, synchronous and asynchronous, that stitches an investigation together.
Error Fingerprinting Issue Grouping, Event Deduplication	pattern	Observability	Deriving a stable identifier from an error's invariant attributes so that many occurrences collapse into one actionable issue - and the two directions in which the heuristic fails damagingly.
Health Checks	pattern	Health Checks	Endpoints that tell the platform whether to route traffic to an instance or restart it — and a well-documented way to amplify an outage.
Ingestion-Query Isolation Write-Read Workload Separation, Analytics Isolation	pattern	Observability	Separating a continuous high-volume write path from a spiky, arbitrary query path so that an expensive query cannot stall ingestion - because a query delay is recoverable and an ingestion gap is not.
Observability in Practice Telemetry, Instrumentation	pattern	Observability	The three signals, what each is actually for, and why the links between them matter more than any of them individually.