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

4 terms shown.

Term	Kind	Topic	What it is
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.
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.
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.