Terminology

2205 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 areas2205 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 Architecture69 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 Architecture64 Streaming & Real-Time Data69 Data Governance & Semantics69 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk64

Kind Any concept794 practice734 pattern368 metric125 case-study77 tool62 protocol45

3 terms shown.

Term	Kind	Topic	What it is
Aspirational and Achievable SLO	practice	SLI, SLO & SLA	The distinction between the reliability a team wishes for and the reliability its current architecture and dependencies can actually deliver.
Journey-Level SLO Per-Journey Availability, User-Facing SLI	practice	SLI, SLO & SLA	Setting reliability targets per user journey rather than per platform or per service, because consequence differs by journey and only a journey-level measurement reflects what a user experienced.
User Journey SLO Critical User Journey, CUJ	practice	SLI, SLO & SLA	Defining reliability targets around what a user is trying to accomplish, measured where the user is, rather than around per-request success rates at the server.