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
Access Pattern Skew Popularity Skew, Zipf Distribution concept Caching for Performance The uneven distribution of requests across keys - which determines whether caching helps at all, and which synthetic load tests systematically fail to reproduce.
Cache Hit Ratio Economics concept Caching for Performance The non-linear relationship between cache hit rate and backend load, which determines whether a cache improvement is worth making.
Cache Stampede Thundering Herd, Dog-Piling concept Caching for Performance The surge of identical expensive requests to the origin when a popular cache entry expires and many concurrent callers all miss at once.
Working Set Hot Data Set concept Caching for Performance The subset of data actually touched in a given window, whose size against the cache's capacity determines the hit rate and therefore how much load reaches the origin.