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

5 terms shown.

Term Kind Topic What it is
Crypto-Shredding Cryptographic Erasure, Key Destruction Deletion, Per-Subject Encryption pattern Data Lifecycle & Retention Encrypting each data subject's personal data under a key unique to them, so that a deletion request is satisfied by destroying the key rather than by rewriting immutable or widely-replicated data.
Crypto-Shredding Cryptographic Erasure practice Data Lifecycle & Retention Making data permanently unreadable by destroying its encryption key, so immutable copies in backups and archives are erased without being modified.
Data Lifecycle practice Data Lifecycle & Retention Managing data from creation through tiering to deletion — the discipline that keeps storage cost and legal exposure bounded.
Hot, Warm and Cold Data concept Data Lifecycle & Retention Classifying data by how frequently and how urgently it is accessed, so each tier can be stored on media priced for that access pattern.
Identity-Record Separation Pseudonymous Subject Reference, Retention-Erasure Split pattern Data Lifecycle & Retention Holding regulated business records under a pseudonymous reference and the reference-to-person mapping in a separate governed store, so a retention obligation and an erasure right can both be satisfied.