Portfolio ↗

Terminology

2205 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 areas2205 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 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 concept794 practice734 pattern368 metric125 case-study77 tool62 protocol45

794 terms shown.

Term Kind Topic What it is
Control-Interval Matching Actuation Delay Matching, Feedback Loop Damping concept Failure Modes Setting a feedback loop's control interval to the delay of the thing it actuates - because a controller that adjusts faster than the system can respond amplifies noise instead of correcting error.
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.
Control-Plane Push Amplification Config Fan-Out, xDS Amplification concept Service Mesh The property that one endpoint change can force a configuration push to every proxy in the fleet, making control-plane work scale with proxies multiplied by services rather than with either alone.
Convergence Without Coordination concept CRDTs The property that replicas applying the same set of updates in any order reach the same state, which is what removes the need for a central arbiter.
Conway's Law concept Architecture Fundamentals Systems tend to mirror the communication structure of the organisation that builds them.
Coordinated Omission Closed-Loop Measurement Bias, Omitted Latency Samples concept Load Testing The measurement error in which a load generator stops issuing requests while the system under test is stalled, so the slow samples that a real arrival process would have produced are never recorded.
Coordination Cost Change Coupling Cost, Cross-Team Latency, Lockstep Tax concept Conway's Law The delay and effort imposed on a change by the number of teams and services that must agree and release together - usually the dominant term in delivery lead time, and almost never instrumented.
Coordination Tax Cross-Team Feature Cost, Conway Misalignment Cost concept Conway's Law The permanent, structural cost incurred when service boundaries are drawn on a different axis from the way work arrives - and the reason consolidating services is sometimes an architectural improvement.
Correlated Degradation Demand-Coupled Failure, Peak-Correlated Dependency Risk concept Degradation Modes The condition where a dependency's reliability worsens for the same reason that user demand rises, so the system is least capable exactly when it is most needed.
Correlated Failure Common-Mode Failure, Shared Fate concept Redundancy Failures that are not independent, so redundancy multiplies far less than the arithmetic promises - usually because replicas share code, configuration or a deployment.
Correlated Region Failure Shared-Fate Region Dependency, Region Failure Correlation concept Single vs Multi-Region The shared dependencies that make two regions fail together, which is why multiplying regions multiplies cost but adds far less availability than independence arithmetic predicts.
Cost Driver Scaling Driver, Cost Dimension concept Architecture Cost Modelling The measurable quantity whose growth causes a cost to grow - identifying it correctly is what makes a cost model predictive rather than descriptive.
Cost of Delay concept Portfolio Prioritisation The economic loss per unit of time that a decision or delivery is postponed, which turns prioritisation from opinion into arithmetic.
Cost Telemetry Lag Billing Data Delay, Spend Reporting Latency concept Cost Governance The delay between spend being incurred and appearing in billing data, which sets a floor on how fast any detective cost control can possibly react and explains why budget alerts arrive after the money is gone.
Cost versus Reliability concept Cost vs Reliability Reliability is bought with redundancy and headroom, both of which cost money — so the target must be chosen rather than assumed.
Cost vs Reliability Trade-off concept Cost & FinOps The non-linear relationship between availability and spend, which makes each additional nine roughly an order of magnitude more expensive.
Cost-Bearing Abstraction Budgeted Abstraction, Abstraction Over Finite Resources concept Abstraction & Encapsulation The principle that any abstraction which lets a caller express arbitrary intent over a shared finite resource must also expose a budget - otherwise the feature is a denial-of-service surface.
Counter Reset Handling Monotonic Counter Semantics, Rate Reset Compensation concept Metrics The rule that a decrease in a cumulative counter is interpreted as a process restart rather than as negative work, which is what allows rates to survive deploys and what makes gauges-as-counters silently wrong.
Counter, Gauge and Histogram concept Metrics The three fundamental metric types, distinguished by what they represent over time and by which aggregations are valid.
Coupling concept Architecture Fundamentals The degree to which one component must know about, or change alongside, another.
Coupling in Practice concept Coupling The kinds of coupling that actually hurt, ranked by how much they constrain independent change.
Coverage Drift Shrinking Scope, Control Reach Decay concept Continuous Controls Monitoring A control operating perfectly on a diminishing share of the estate - passing every assessment of the systems it covers while providing progressively less assurance overall.
Covering Index Index-Only Scan concept Indexing An index that contains every column a query needs, so the query is answered from the index without reading the table at all.
CRDT Conflict-Free Replicated Data Type concept CRDTs A data structure whose concurrent updates always merge to the same result regardless of order, removing the need for coordination or conflict resolution.
Credibility Budget Influence Capital, Spending Political Credit concept Influence Without Authority The finite standing an architect has to override or refuse, earned by being useful and by being right about things that mattered - and spent deliberately on the small number of decisions where inconsistency is…
Cross-Border Transfer Mechanism SCCs, Adequacy Decision, Transfer Impact Assessment concept Cross-Border Transfer The legal basis required to move personal data from one jurisdiction to another, and the architectural evidence needed to support it.
Cross-Cutting Concern concept Separation of Concerns A responsibility that legitimately appears throughout a system rather than in one module, such as logging, authorisation, tracing or transaction management.
Cross-Functional Requirement concept Functional vs Non-Functional A quality the system must exhibit across its features rather than a behaviour it must perform, so named because it cuts across all functionality.
Cross-Zone Data Transfer concept Availability Zones Charges incurred when data moves between availability zones within a region — invisible on architecture diagrams and a recurring surprise on cloud bills.
Cross-Zone Load Balancing concept Load Balancing Whether a load balancer node distributes traffic to targets in all zones or only its own — a setting that affects both balance and data transfer cost.
DAG Dependency concept Batch Orchestration The declared edge stating that one task must not start until another has succeeded, and the difference between that and merely running later.
Data Access Model concept Data Access Models The scheme by which permission to data is granted, whether by role, by attribute, by purpose, or by request with expiry.
Data Gravity Data Inertia, Locality Pull, Egress Pull concept Network & Egress Costs The tendency of large data to attract compute and services toward it, because moving data across billed or slow boundaries is expensive while moving computation to the data is cheap.
Data Lakehouse concept Data Architecture A pattern that puts warehouse-style transactions, schema and governance on top of cheap open-format object storage.
Data Layout Partitioning and Clustering, File Organisation, Pruning Effectiveness concept Storage Layout & Partitioning How table data is physically organised into partitions and files, which determines how much can be skipped at query time - and is the dominant factor in analytical cost and performance, ahead of cluster size.
Data Lineage View concept Data-Flow Diagrams A view showing how data moves and is transformed through a system, independent of the components that do the moving.
Data Mesh concept Data Architecture An organisational approach that gives domain teams ownership of their analytical data as a product, with a self-serve platform and federated governance.
Data Mesh Federated Governance concept Data Governance & Semantics Central agreement on the rules that must be global, with domain autonomy over everything else.
Data Mesh in Practice concept Data Mesh Decentralising data ownership to the domains that produce it, with a self-serve platform and federated governance — an organisational change more than a technical one.
Data Minimisation concept Lawful Basis & Purpose Limitation Collecting and retaining only the personal data actually necessary for the stated purpose, treated as an architectural constraint rather than a policy statement.
Data Plane Proxy Envoy, Sidecar Proxy concept Service Mesh Networking The per-workload proxy that actually carries mesh traffic, applying mTLS, retries, timeouts, routing and telemetry outside the application.
Data Platform Architecture Analytical Platform Architecture, Data Stack Architecture concept Data Platform Architecture The arrangement of ingestion, storage, transformation, serving and governance that decides whether analytical data arrives on time, means the same thing to everyone and costs a predictable amount.
Data Platform Tenancy concept Data Platform Tenancy How a shared data platform separates domains and customers across storage, compute, catalogue and access control.
Data Product Published Dataset, Owned Data Asset, Analytical Interface concept Data Products A dataset published deliberately as an interface with a named owner, documented semantics, quality guarantees and a change policy - as distinct from a table that consumers happen to be able to reach.
Data Product concept Data Products A curated, documented, owned dataset treated as a product with consumers, a service level and a lifecycle, rather than as the output of a pipeline.
Data Proximity Compute-Data Locality, Edge Distance Problem, Origin Pull concept Edge Rendering The observation that moving compute toward the user moves it away from the data, so edge execution helps only for computations that do not need a central round trip - and hurts for the ones people most want to…
Data Quality Dimensions concept Data Quality Dimensions The standard axes along which data quality is measured, which turn a vague complaint into a testable assertion.
Data Residency Data Localisation concept Data Residency A requirement that data be stored, and sometimes processed, within a specified geography.
Data Steward concept Data Stewardship The named individual accountable for the definition, quality and appropriate use of a specific data domain.
Data Subject Access Request DSAR, SAR concept Data Subject Rights An individual's request for a copy of the personal data an organisation holds about them, which must be fulfilled completely within a statutory deadline.
Data Warehousing concept Data Warehousing A separate analytical store modelled for questions rather than transactions, physically isolated from the systems that generate the data.
Data-Plane Fail-Static Window Mesh Survival Window, Control-Plane Outage Headroom concept Service Mesh Operations How long a service mesh keeps carrying traffic after its control plane is gone, set by certificate lifetime and pod churn rather than by anything the mesh reports as healthy.
Data-Plane Upgrade Skew Proxy Version Skew Window, Mesh Upgrade Skew concept Service Mesh Operations The window during which a mesh runs proxies of more than one version alongside a control plane that supports only a bounded range of them, which is what makes every mesh upgrade a scheduled fleet restart rathe…
Database Index concept Data Architecture A secondary structure that lets the engine find rows without scanning, trading write cost and storage for read speed.
Deadline Exceeded concept Timeouts & Deadlines The error returned when a request's overall budget expires — semantically distinct from a per-hop timeout, and a signal that must not be retried blindly.
Deadline-Derived Queue Depth Deadline-Bounded Queue concept Concurrency The rule that a request queue's maximum depth comes from the client's deadline and the service's completion rate, so the queue can never hold work that will expire before it is served.
Debt Interest Rate Cost Per Unit Time, Debt Triage Axis concept Technical Debt How much a piece of technical debt costs per unit time in slowed delivery, incidents and effort - which, paired with the cost to fix, is what separates debt worth paying down from debt that merely looks unpleasant.
Decision Debt Unrecorded Decision Backlog, Undocumented Choice Accumulation concept Decision Practice The accumulated set of choices a system embodies but nobody wrote down, which turns every later change into an archaeology exercise and makes safe modification depend on individual memory.
Decision Feedback Delay Judgement Lag, Architectural Feedback Latency concept Career Development The 12 to 36 months between making an architectural decision and observing its consequences, which is long enough that the loop stays open unless the record itself carries the falsifying signal.
Decision Rights Boundary Decision Scope Line, Local Versus Enterprise Decision concept EA Domains The line separating choices a team may make alone from choices that bind other teams - drawn by where the consequence of a mistake lands, not by the cost, size or difficulty of the decision.