Terminology
991 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 areas991
Architecture Fundamentals38
Distributed Systems73
Data Architecture71
Cloud Architecture55
Networking51
API & Integration Architecture45
Reliability & Resilience40
Observability33
Performance & Capacity Engineering34
Security Architecture50
Cost Architecture & FinOps30
Business Architecture28
Architecture Communication27
Enterprise Architecture27
Legacy Modernization27
AI-Era Architecture34
Software Architecture & Engineering37
Architecture Patterns34
Architecture Decision-Making30
The Architect's Meta-Skills27
Delivery & Release Engineering20
Platform Engineering & Developer Experience20
Testing & Quality Architecture20
Data Platform Architecture20
Streaming & Real-Time Data20
Data Governance & Semantics20
Frontend & Experience Architecture20
Edge, Mobile & IoT20
Regulatory & Data Protection Architecture20
Assurance, Audit & Model Risk20
20 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Adoption Curve | metric | Platform Adoption | The proportion of teams actually using a platform capability over time, which is the only honest measure of whether the platform is working. |
| Base Image Currency | metric | Container Image Strategy | How far behind the fleet's running images are from their patched base, which is the number that decides how fast a critical vulnerability can be closed. |
| 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. |
| Deprecation Window | practice | Platform API Deprecation | The stated period between announcing that an internal interface will be removed and removing it, with the removal actually happening at the end. |
| Enabling Team | pattern | Platform Team Topologies | A team whose output is other teams' increased capability, working alongside them temporarily and deliberately removing itself. |
| Ephemeral Environment | pattern | Developer Environments | A full environment created on demand for one change and destroyed afterwards, which removes the queue for shared environments and the drift within them. |
| Golden Path | pattern | Paved Road & Golden Path | One opinionated end-to-end route from idea to production that is genuinely easier than the alternatives, and is supported rather than mandated. |
| Inner Loop Latency | metric | Inner Loop & Outer Loop | The time from changing a line to observing its effect, repeated dozens of times a day and therefore the highest-leverage number in developer experience. |
| Internal Consumer SLO | metric | Platform SLOs | A reliability commitment made to teams who cannot switch supplier, which is why it must be measured from their side rather than from the platform's. |
| 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. |
| Namespace Tenancy | pattern | Platform Tenancy | Isolating teams within a shared cluster by namespace plus quota plus network policy, and being explicit about what that does not isolate. |
| Paved Road Telemetry | practice | Platform Telemetry | Instrumenting the platform's own usage — where teams succeed, where they stall, where they leave — so its roadmap is driven by evidence. |
| 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 User Research | practice | Platform Engineering | Treating engineers as users whose actual behaviour is observed rather than assumed, which is what separates a platform from a set of shared tools. |
| 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. |
| Provisioning Self-Service | practice | Self-Service Provisioning | Teams obtaining infrastructure without a ticket, within bounds that make the request safe by construction rather than by review. |
| 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 Scaffolding | tool | Service Templates | Generating a new service with observability, CI, security and ownership already wired in, so the standard is the default rather than a checklist. |
| Showback | practice | Platform Funding | Reporting each team's share of platform and infrastructure cost without actually charging it, to change behaviour without creating a market. |
| Sidecar Overhead | metric | Service Mesh Operations | The latency, memory and failure surface a mesh proxy adds per pod, which is the price of what the mesh provides and is frequently unmeasured. |
Nothing on this page matches. Search the whole glossary.