Portfolio ↗

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
Kind Any concept801 practice736 pattern377 metric127 case-study77 tool62 protocol45

21 terms shown.

Term Kind Topic What it is
Cluster Architecture practice Cluster Architecture How many clusters, how they are divided, and what shares fate — decisions about blast radius and operational burden rather than about capacity.
Container Image Strategy Base Image Policy, Golden Image practice Container Image Strategy The organisational decision about where images come from, what they are built on, and how a base layer fix reaches everything already deployed.
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.
Escape Hatch Progressive Disclosure, Drop-Down Path practice Abstraction Level Choice A supported route from a platform's simple default down to the underlying primitives - so a team with an unusual need adapts within the platform rather than leaving it.
Golden Path Paved Road, Paved Path practice Paved Road & Golden Path The supported, documented, pre-integrated way to do a common task, made easier than any alternative rather than mandatory.
Object Count Quota Resource Count Limit, Control-Plane Quota practice Platform Tenancy A per-tenant limit on how many control-plane objects a team may create, which is the control that prevents one team's design choice from exhausting the shared configuration store every other team depends on.
Pager Boundary Platform On-Call Boundary, Injected Component Ownership Line practice Platform Engineering The written line in a platform contract that says which symptoms page the platform team and which page the consuming team, and how a single signal tells the two apart during an incident.
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 API Deprecation practice Platform API Deprecation Retiring a platform capability that other teams depend on, with the migration burden treated as the platform's problem rather than theirs.
Platform as Product practice Platform Funding Running an internal platform with a product manager, a roadmap, identified users and measured adoption, rather than as a project with an end date.
Platform Telemetry practice Platform Telemetry Instrumentation of the platform itself — who uses which capability, how long it takes and where it fails — used as product evidence, not just operations.
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.
Provisioning Reconciliation Orphan Sweep, Convergent Provisioning practice Self-Service Provisioning Running a scheduled comparison between what a self-service platform intended to create and what actually exists in the cloud account, so partial failures become a tracked number rather than an invoice surprise.
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.
Residual Caller Tail Deprecation Long Tail, Last Caller Problem practice Platform API Deprecation The handful of callers left at the end of a deprecation who will not move on their own, and the mechanisms that clear them so the removal date holds instead of slipping.
Self-Service Provisioning practice Self-Service Provisioning A developer obtaining infrastructure through an automated interface bound by policy, with no ticket and no human approval in the path.
Service Maturity Scorecard Production Readiness Scorecard practice Platform Adoption An automated per-service assessment against the organisation's operational standards, visible to the owning team.
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.
Template Propagation Getting Improvements Into Existing Services, Template Drift practice Service Templates The mechanism by which improvements to a service template reach the services already generated from it - the hardest part of the template model and the part most often omitted.
Time to First Success Time to Hello World, Onboarding Latency practice Platform Adoption How long it takes a new team to get something working on the platform - the single best proxy for developer experience and the strongest predictor of adoption.
Usage Telemetry Who Calls This, Consumer Visibility practice Platform Telemetry Per-capability, per-consumer usage data about a platform's own surfaces - the precondition for every deprecation, roadmap and change-impact decision a platform team makes.