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

729 terms shown.

Term	Kind	Topic	What it is
Bias and Fairness Control	practice	Bias & Fairness Controls	Measuring and constraining disparate outcomes across groups, where the definition of fairness must be chosen deliberately because the definitions are mutually incompatible.
Billable-Event Metering Contract-Aligned Metering, Obligation-Point Metering	practice	Licence & Vendor Costs	Recording the event a contract actually charges for at the point in the system where that obligation is created, rather than inferring it from delivery telemetry that caching and retries make unreliable.
Blameless Postmortem Learning Review, Incident Retrospective, Non-Attributive Analysis	practice	Postmortems	An incident analysis structured so that participants can disclose what actually happened without personal risk - which is a technical requirement for accurate information, not a cultural courtesy.
Blameless Postmortem	practice	Reliability & Resilience	An incident review that seeks the systemic conditions that made a failure possible, explicitly excluding individual fault.
Blast Radius Analysis	practice	Fault Isolation	Determining, for each component, exactly what fails and who is affected when it fails completely.
Blast Radius Reduction	practice	Cloud Architecture	The set of deliberate partitions — accounts, regions, zones, cells, tenants, deployment stages — that bound how far any single failure or compromise can reach.
Blast Radius Staging Graduated Rollout, Progressive Shedding	practice	Failover	Applying a change or a traffic shift in increasing increments gated on health, so that a wrong decision affects a bounded population before it affects everyone.
Bottleneck Analysis	practice	Bottleneck Analysis	Finding the single resource that limits the system, because improving anything else changes nothing.
Bottom Line Up Front	practice	Written Communication	Placing the conclusion and the requested action in the first lines, on the assumption that most readers will not reach the end.
Boundary Volatility Test	practice	Service Boundaries	Evaluating a proposed service boundary by asking whether the things on either side change for different reasons and at different rates.
Break-Glass Access Emergency Access, Just-in-Time Elevation	practice	Identity & Access Management	A pre-agreed, heavily audited path to elevated privilege for emergencies, replacing standing administrative access.
Breaking-Point Testing Test to Failure, Constraint Discovery	practice	Load Testing	Pushing a load test past the target until the system fails, because the purpose of a load test is to locate the constraint and the failure mode rather than to confirm a number.
Budget Guardrail	practice	Cost Governance	An automated control that constrains or alerts on spend before an invoice arrives, rather than reporting overspend after the fact.
Build Provenance Artefact Attestation, SLSA Provenance	practice	Supply Chain Security	A signed, verifiable statement of what was built, from which source, by which builder, with which dependencies - so a consumer can check that an artefact corresponds to reviewed source.
Build Reproducibility Reproducible Build, Deterministic Build	practice	Build Reproducibility	The same source input produces a bit-for-bit identical artifact, on any machine, at any time.
Build versus Buy	practice	Build vs Buy	Whether to build a capability or acquire it — decided primarily by whether the capability differentiates, not by whether you could build it.
Build-vs-Buy Total Cost	practice	Build vs Buy	Comparing a purchased solution against building one on the full lifetime cost, including the maintenance and opportunity costs that estimates omit.
Bulk and Batch API Design	practice	REST Design	Endpoints that accept many items in one call, and the partial-failure semantics that make them either useful or dangerous.
Business Case Structure	practice	Business Cases	The argument format that gets technical investment funded — problem, options, quantified benefit, cost, risk and a recommendation.
Business Cases	practice	Business Cases	The argument that an investment is worth making — where architects supply the cost, risk and option value rather than the enthusiasm.
Business Continuity	practice	Business Continuity	Keeping the business operating through disruption — a broader discipline than disaster recovery, and one that includes not using the system at all.
Business Correlation Identifier Domain Trace Key, Entity Correlation	practice	Correlation IDs	A domain identifier - shipment, order, trip, claim - carried on every log line, event, job and external call, answering the question distributed tracing cannot: what happened to this thing, over days, across s…
Business Impact Analysis	practice	Business Continuity	Determining which business processes must be restored, how quickly, and what the consequence of not doing so is — the input from which recovery targets are derived.
Business Metric Alerting Outcome Monitoring	practice	Business Metrics	Alerting on product outcomes rather than on technical signals, because it is the only way to catch failures where the system works correctly and produces the wrong result.
Business Metric Instrumentation	practice	Business Metrics	Emitting metrics for business outcomes — orders, payments, signups — alongside technical telemetry, so incidents can be detected and prioritised by impact.
Business Understanding	practice	Business Understanding	Knowing how the organisation makes money, what it is trying to achieve, and what would damage it — without which architectural judgement has no basis.
Business-Cycle Observation Window Full-Cycle Shutdown Soak, Longest-Period Consumer Watch	practice	Decommissioning	Setting the period over which you watch for remaining consumers from the system's longest business cycle rather than from a round number of days, because a 30-day watch cannot see an annual job.
C4 Model	practice	Architecture Communication	A set of four nested diagram levels — context, container, component, code — that keeps each diagram at one consistent level of abstraction.
C4 Model in Practice	practice	C4 Model	Four nested levels of diagram — context, container, component, code — whose value is controlling altitude rather than the notation itself.
Cache Key Completeness	practice	Reverse Proxies	The requirement that a cache key capture every input varying the response - the property whose violation turns a caching bug into a data leak.
Cache-Loss Survivability Cache Failure Blast Radius, Origin Protection	practice	Cache Invalidation	Designing so that losing the cache degrades the system rather than destroying it - because a cache absorbing most of the read traffic is a capacity dependency, not an optimisation.
Calibrated Confidence	practice	Judgement Under Uncertainty	Expressing certainty in proportion to actual evidence, so that stated confidence carries information rather than conveying personality.
Can-I-Deploy Gate Deployment Compatibility Query, Contract Broker Gate	practice	Contract Testing at Scale	A check at deploy time that asks whether this service version is verified against the consumer and provider versions actually running in the target environment - turning contract tests from documentation into …
Capability Flag Partner Capability, Feature Declaration	practice	Integration Patterns	Representing genuine differences between integrated partners as explicit declared capabilities, rather than as variant fields in a shared canonical model.
Capability Heat Map	practice	Capability Mapping	A capability map coloured by a chosen dimension — maturity, cost, risk, or strategic importance — to make patterns visible to non-technical stakeholders.
Capability Mapping	practice	Capability Mapping	Laying out capabilities hierarchically and overlaying information — systems, cost, health, differentiation — to make investment decisions visible.
Capability Maturity Assessment	practice	Business Capabilities	Rating each business capability on how well it is currently performed, so investment can be directed at the gap between importance and maturity.
Capability-to-Application Mapping	practice	Capability Maps in EA	Linking each business capability to the systems that support it, which is what converts two inventories into an analysis tool.
Capacity Borrowing Capacity Reallocation, Priority Eviction, Shared Fleet Priority	practice	Architectural Drivers	Serving an unpredictable new load from an existing shared fleet by displacing lower-priority work, which requires that the displaceable work be identified and shaped to be interruptible before the demand arrives.
Capacity Modelling	practice	Capacity Modelling	Predicting the resources a workload will need, from measured unit costs and a demand forecast, with deliberate headroom.
Capacity Planning	practice	Reliability & Resilience	Deciding in advance how much capacity will be needed, given growth, seasonality and failure scenarios, and ensuring it can be there in time.
Cardinality Budget Series Budget, Label Quota	practice	Cardinality	A measured, owned limit on the number of distinct metric series a team may create - the control that converts an invisible cost externality into a visible constraint.
Career Development	practice	Career Development	How architectural careers actually progress — through scope, judgement and demonstrated outcomes rather than through accumulated technology knowledge.
Catch-Up Throttling Recovery Rate Limiting, Drain Control	practice	Streaming & Real-Time Data	Deliberately limiting how fast a recovered consumer drains its backlog, so that recovery does not become a second and larger incident.
CDC Pipeline Design	practice	CDC Pipeline Design	The concerns that turn log-based change capture from a demo into something that can be relied on — snapshots, ordering, schema change and replay.
Certificate Lifecycle Management	practice	TLS & Certificates	Issuing, deploying, monitoring and renewing certificates automatically, because manual tracking reliably produces outages.
Certified Report	practice	BI Governance	A small set of reports explicitly endorsed as authoritative, with an owner and a review cadence, distinguished from everything else people have built.
Change-Aware Test Selection Affected Test Selection, Predictive Test Selection	practice	Pipeline Architecture	Running only the tests a change could affect, determined from a dependency graph - with periodic full runs to verify the selection itself.
Change-Reason Cohesion Single Reason to Change, Axis of Change	practice	Cohesion	The working test for a module boundary - things belong together if they change for the same reason, at the same time, driven by the same stakeholder, and share invariants.
Chaos Engineering	practice	Reliability & Resilience	Deliberately injecting failure into a system to discover, before an incident does, which of your resilience assumptions are false.
Chaos Engineering in Practice	practice	Chaos Engineering	Deliberately injecting failure into production to verify that resilience mechanisms work — an experiment with a hypothesis, not vandalism.
Chaos Experiment	practice	Chaos as a Test	A controlled fault injected into a system to test a written hypothesis about how it should degrade.
Characterisation Test Golden Master Test, Approval Test, Behaviour Snapshot	practice	Application Decomposition	A test that records what a system currently does - bugs included - rather than what it should do, providing the safety net that makes changing an untested legacy system possible at all.
Chargeback and Showback	practice	Cost & FinOps	Attributing cloud cost to the teams that generate it — either informationally (showback) or by moving it onto their budget (chargeback).
Chunk Boundary Strategy	practice	Chunking & Retrieval	How source documents are split for embedding, which determines whether retrieved passages are self-contained and coherent.
CI/CD Continuous Integration, Continuous Delivery	practice	CI/CD	Integrating continuously and keeping the software always releasable — a discipline about batch size, with automation as its enabler.
CIDR Planning	practice	VPC Design	Allocating non-overlapping address ranges across an estate in advance, because ranges cannot be resized and overlaps prevent connectivity.
Claim Provenance As-Of Metadata, Source-Tagged Data	practice	Data Architecture	Storing every externally sourced value with its timestamp, its source and a confidence derived from that source's history - so that downstream decisions about staleness are explicit rather than accidental.
Classification Propagation Label Inheritance, Lineage-Aware Classification, Derived Sensitivity	practice	Sensitivity Labelling	Carrying a column's sensitivity classification through every derived table, view and export, so that copying restricted data into an aggregate does not silently strip its protection.
Classification Propagation Labels Travelling Through Lineage, Derived-Data Sensitivity	practice	Sensitivity Labelling	Carrying a sensitivity label through every derivation, so a restricted column copied into an aggregate, a training set or an export remains subject to its controls.