Portfolio ↗

Terminology

2185 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 areas2185 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture89 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture81 Cost Architecture & FinOps66 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization66 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 concept785 practice729 pattern362 metric125 case-study77 tool62 protocol45

4 terms shown.

Term Kind Topic What it is
Bloom Filter Cache Guard pattern Caching Strategies Placing a Bloom filter in front of an expensive lookup so that keys which certainly do not exist never reach it.
Caching Strategies pattern Caching Strategies Which cache pattern to use, how staleness is bounded, and the failure modes that only appear under load.
Caching Strategies in Practice Cache-Aside, Write-Through, Read-Through pattern Caching Strategies The write and read strategies, the stampede that takes down origins, and why cache invalidation deserves its reputation.
Integrated Cache Tier Cache-Behind-the-Client, Storage-Managed Cache, Transparent Cache pattern Caching Strategies Placing the cache inside the storage layer's own client rather than in each calling application, so invalidation is driven by the change stream and consistency semantics are defined once instead of per team.