Portfolio ↗

Data Lifecycle & Retention

How long data is kept, where it ages to, and how it is actually deleted.

4Questions
11Flashcards
5Terms
Drill this topic All of Data Architecture
Questions

4 to work through

  1. advanced

    A GDPR erasure request arrives for a customer. Where does their data actually live, and what makes this expensive to retrofit?

    2 min answer
  2. advanced

    A consumer fintech accumulates transaction, behavioural and derived data. How should retention, archival, deletion and regulatory holds be designed so they do not conflict?

    2 min answer
  3. advanced

    A customer exercises their right to erasure. List every place their data plausibly exists in a mature architecture and how each is handled.

    3 min answer
  4. advanced

    A file storage platform must permanently delete a user's data on request, while maintaining backups, replicas, caches and search indexes. What makes this genuinely difficult, and how is it designed?

    3 min answer
Terminology

5 terms in this topic

pattern

Crypto-Shredding

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…

 practice

Crypto-Shredding

Making data permanently unreadable by destroying its encryption key, so immutable copies in backups and archives are erased without being modified.

 practice

Data Lifecycle

Managing data from creation through tiering to deletion — the discipline that keeps storage cost and legal exposure bounded.

 concept

Hot, Warm and Cold Data

Classifying data by how frequently and how urgently it is accessed, so each tier can be stored on media priced for that access pattern.

 pattern

Identity-Record Separation

Holding regulated business records under a pseudonymous reference and the reference-to-person mapping in a separate governed store, so a retention ob…
Data Architecture

Neighbouring topics

Data Architecture

General material on structuring, storing and governing data.

10 quiz 31 cards 25 terms

Relational Modelling

Normalisation, keys, constraints and the invariants a schema enforces.

3 quiz 10 cards 4 terms

NoSQL Stores

Key-value, document, wide-column and graph — what each buys and forbids.

5 quiz 13 cards 4 terms

Indexing

Designing indexes per query shape, and paying for them on every write.

5 quiz 12 cards 6 terms

Query Optimisation

Reading a plan, fixing statistics, and finding the real bottleneck.

3 quiz 11 cards 4 terms

Transactions & Isolation

ACID, isolation levels, and the anomalies each level permits.

3 quiz 10 cards 4 terms

Replication

Primaries, replicas, lag, and synchronous versus asynchronous durability.

4 quiz 14 cards 6 terms

Partitioning & Sharding

Splitting data across machines, and the one-way door of a partition key.

6 quiz 12 cards 10 terms

Caching Strategies

Cache-aside, read-through, write-through and where each belongs.

7 quiz 15 cards 6 terms

Cache Invalidation

Stampedes, penetration, staleness windows and versioned keys.

3 quiz 7 cards 2 terms

CQRS

Separating the write model from the read models that serve queries.

4 quiz 10 cards 5 terms

Event Sourcing

Storing the change log as the system of record, and what that costs forever.

5 quiz 13 cards 4 terms

Change Data Capture

Turning a database's replication log into a stream, and its coupling risk.

5 quiz 14 cards 5 terms

Data Warehousing

Dimensional modelling, star schemas and analytical workloads.

4 quiz 13 cards 3 terms

Data Lakes & Lakehouses

Open formats on object storage with transactional metadata on top.

4 quiz 11 cards 4 terms

ETL & ELT

Where transformation happens, and how much raw history you keep.

3 quiz 9 cards 3 terms

Streaming Data

Windowing, watermarks, late arrivals and exactly-once semantics.

3 quiz 10 cards 2 terms

Data Governance

Ownership, lineage, quality, catalogues and who may see what.

3 quiz 9 cards 4 terms

Polyglot Persistence

Choosing a store per workload, and the operational cost of variety.

6 quiz 12 cards 4 terms