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
27 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Cluster Multi-Tenancy Soft Multi-Tenancy, Namespace Tenancy | concept | Platform Tenancy | Multiple teams or workloads sharing one cluster, isolated by namespaces, quotas and policy rather than by separate infrastructure. |
| Cluster Split Axis | concept | Cluster Architecture | The dimension along which the estate is divided into clusters — the single decision that determines both blast radius and operational load. |
| Cognitive Load | concept | Platform Team Topologies | The total amount a team must hold in mind to do its work, treated as a hard constraint on how much a team can own. |
| Compatibility Window Overlap Window, Dual-Version Period | concept | Platform APIs | The period during which two versions of a caller or message must both work, set by deployment and queue mechanics rather than by how many consumers there are, which is why even a single internal consumer requi… |
| Contention Blind Spot Single-User Environment Blindness, Concurrency Fidelity Gap | concept | Developer Environments | The class of defects a one-user test environment cannot exhibit at all - lock waits, pool exhaustion, races and plan flips - because they require concurrency and production-shaped data rather than correct code. |
| 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. |
| 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… |
| Escape Hatch Drop to Primitives, Graduated Abstraction, Opt-Out Path | concept | Abstraction Level Choice | A supported way for a team to bypass part of a platform abstraction and work with the underlying primitives - which is what makes an abstraction safe to adopt and what supplies the platform's most valuable roa… |
| Fleet-Wide Change Reach Platform Change Propagation | concept | Service Templates | How long it takes a platform change to reach the majority of the services built on it - the measure of whether a platform can actually change anything. |
| Image Pull Amplification Per-Node Image Cost, Cold Node Pull Cost | concept | Container Image Strategy | The property that a container image's size is paid on every node that has never seen that version, so its real cost scales with node churn and scale-out events rather than with release frequency. |
| Inner Loop | concept | Inner Loop & Outer Loop | The edit-build-test cycle a developer repeats dozens of times an hour, entirely on their own machine or environment. |
| Inner-Loop Multiplier Frequency Times Duration, Daily Friction Cost | concept | Inner Loop & Outer Loop | The reason inner-loop friction dominates developer productivity - the loop runs dozens of times a day, so a small duration difference multiplies into hours, while the outer loop runs a few times. |
| Internal Developer Platform IDP, Developer Platform | concept | Internal Developer Platform | The curated set of self-service capabilities that lets product teams build, deploy and operate software without filing tickets against infrastructure. |
| Leaky Abstraction Cost | concept | Abstraction Level Choice | What a consumer pays when a platform abstraction hides a mechanism they must nonetheless understand to diagnose or tune it. |
| Noisy Neighbour Resource Contention, Co-Tenant Interference, Shared-Fate Degradation | concept | Platform Tenancy | One workload degrading others by consuming a shared resource - and specifically the resources nobody set limits on, such as control-plane capacity, node network bandwidth and local disk. |
| Platform Abstraction Level | concept | Abstraction Level Choice | How far a platform hides the underlying infrastructure, and the leak-versus-flexibility trade it makes at that height. |
| Platform API | concept | Platform APIs | The programmatic contract through which teams consume platform capabilities, and the thing that must stay stable while everything behind it changes. |
| Platform Contract | concept | Platform APIs | The platform's promise to its consumers about interface stability, behaviour and support, treated with the same seriousness as an external API. |
| Platform Engineering | concept | Platform Engineering | Building internal products that reduce the cognitive load on delivery teams — with self-service as the property that separates it from a service desk. |
| Platform Funding Model | concept | Platform Funding | How internal platform work is paid for, which determines what the platform optimises for and whether it survives a budget cycle. |
| Preventive Control Placement | concept | Guardrails vs Gates | Choosing where in the lifecycle a control acts — at authoring, at admission or after the fact — which determines both its strength and its cost. |
| Selector Dependency Label Contract, Implicit Platform Dependency | concept | Cluster Architecture | A production dependency that exists only as a string matching a label or annotation, so it is invisible to code search and to release notes, and a platform upgrade that renames the label silently removes it. |
| Service Catalogue Entry | concept | Internal Developer Platform | The record that makes a service a first-class object in the platform — owner, dependencies, docs, runbooks and health in one place with a single identity. |
| Service Mesh Operational Cost | concept | Service Mesh Operations | The ongoing engineering burden a mesh imposes — upgrades, proxy debugging, latency overhead and control-plane availability — weighed against the capabilities it provides. |
| Ticket Ops Ticket-Driven Operations | concept | Self-Service Provisioning | An operating model where teams obtain infrastructure and change by requesting it from another team, making that team a queue. |
| Voluntary Adoption Pull-Based Adoption, Chosen Uptake, Non-Mandated Usage | concept | Platform Adoption | Usage of a platform by teams that could have chosen otherwise - which is the only measurement that indicates whether the platform is actually useful, and which a mandate permanently destroys. |
Nothing on this page matches. Search the whole glossary.