Portfolio ↗

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
API Error Design Problem Details, RFC 9457 practice API Error Handling Returning failures in a consistent machine-readable structure that tells a client what went wrong, whether to retry, and what to do about it.
Outcome Certainty Taxonomy Retryability Classification, Four-State Error Model pattern API Error Handling Classifying every external response into definitely-failed-retryable, definitely-failed-terminal, definitely-succeeded, or unknown - and giving the fourth state a real resolution path rather than a guess.
Problem Details RFC 9457, RFC 7807 protocol API Error Handling A standard JSON structure for HTTP error responses, giving machine-readable type, human-readable detail, and room for extensions.
Retryable Error concept API Error Handling An error whose cause may resolve on its own, which a client may safely attempt again — as distinct from one that will fail identically.