Learn AI ↗

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
Kind Any concept379 practice294 pattern166 metric55 tool36 protocol35 case-study26

5 terms shown.

Term Kind Topic What it is
Bake Time concept Multi-Region Rollout The deliberate wait between rollout steps, sized by how long the fault you are watching for takes to appear.
Build Attestation concept Supply-Chain Provenance A signed statement about how an artifact was produced — by which builder from which source — that a deployment gate can verify rather than trust.
Environment Ladder concept Environment Strategy The ordered set of environments a change climbs, where each rung is justified by a distinct claim it can prove that the one below cannot.
Pipeline Stage Contract concept Delivery & Release Engineering What each pipeline stage promises the next — an artifact of a stated shape plus a specific claim about it that has been verified.
Rolling Update Surge concept Deployment Strategies The extra capacity a rolling deployment temporarily adds, and the unavailability it is permitted, which together decide whether the rollout is safe under load.