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

4 terms shown.

Term	Kind	Topic	What it is
Interest-Based Negotiation Principled Negotiation, Positions vs Interests	practice	Negotiation	Negotiating against what each party actually needs rather than what they have asked for, which opens options that the stated positions foreclose.
Last Safe Start Date Programme Latest Start, Deadline Backstop Date	metric	Negotiation	The externally imposed deadline minus the programme's duration and contingency - the date an architect computes and owns, which competes for funding in a way the distant vendor deadline does not.
Negotiation	practice	Negotiation	Reaching decisions with people whose objectives differ — by working from interests rather than positions, and by making trades explicit.
SLA Measurement Point Measurement Boundary, Observation Point	concept	Negotiation	The place in the request path where an availability or latency commitment is observed, which decides what the number means and is where nearly every SLA dispute actually originates.