Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Regulatory & Data Protection Architecture”
Obligation Mapping
Translating each legal or regulatory requirement into the specific design constraints it imposes, so that compliance becomes a set of testable properties rather than a document.
Personally Identifiable Information
Data relating to an identifiable person — a category far broader than name and address, and the trigger for most regulatory obligation.
Capital One's Data Centre Exit
A major US bank closed all eight of its data centres and moved fully to public cloud, treating governance automation as the enabling technology rather than a constraint.
Change Data Capture
Publishing a stream of a database's row-level changes by reading its replication log, without modifying the application that owns it.
Control Plane and Data Plane
The separation between the machinery that makes changes to a system and the machinery that serves its traffic.
Cross-Zone Data Transfer
Charges incurred when data moves between availability zones within a region — invisible on architecture diagrams and a recurring surprise on cloud bills.
Data Lakehouse
A pattern that puts warehouse-style transactions, schema and governance on top of cheap open-format object storage.
Data Mesh
An organisational approach that gives domain teams ownership of their analytical data as a product, with a self-serve platform and federated governance.
Data Minimisation
Collecting and retaining only what a stated purpose requires, which reduces both regulatory exposure and breach impact at the same time.
Data Residency
A requirement that specific data be stored and sometimes processed only within a defined geography.
Data Retention Policy
A defined rule for how long each class of data is kept, where, and what happens at the end of it.
Data-Flow Diagram
A diagram of how data moves between processes, stores and external entities, with trust boundaries drawn on it.
Layered Architecture
Organising code into horizontal layers — presentation, application, domain, data — where each layer may only call the one beneath it.
Netflix's Recommendation Architecture
Netflix splits personalisation into offline, nearline and online layers so that expensive computation happens ahead of time and the request path stays fast.
Regulatory Constraint
A legal requirement that removes design options — and one that must be established early, because it is not negotiable and is expensive to retrofit.
Product wants to add a recommendation feature using browsing history. Legal asks for a data protection impact assessment. What does architecture need to supply?
What the assessment actually needs from architecture Legal cannot assess a feature description. They need the data facts, which only the design supplies: A data
Six weeks before launch, legal confirms that customer data for one market must be processed and stored in-country. The architecture is single-region in another jurisdiction. What do you do?
Establish exactly what the requirement covers Before designing anything, get three things in writing from legal: which data is in scope — usually a defined cate
Regulatory & Data Protection Architecture
General material on designing under legal and regulatory obligation.
Healthcare Data Protection
PHI handling, minimum necessary access, and audit expectations in clinical systems.
Consent Architecture
Capturing, versioning and propagating consent to every system that acts on the data.
Data Residency
Keeping data within a jurisdiction, including backups, logs and support access.
Data Subject Rights
Access, correction, portability and erasure across systems that never planned for them.
Regulatory Reporting Pipelines
Submissions with fixed deadlines, fixed formats, and a regulator who audits the lineage.
Cross-Border Transfer
The legal mechanism that permits data to leave, and the architecture that respects it.
Digital Sovereignty
Control over data, operations and the operator, beyond where the bytes physically sit.
Erasure vs Immutability
Deletion obligations against event logs, backups and ledgers designed never to forget.
Exit & Concentration Risk
Being able to leave a provider, and what the regulator asks when you cannot.
Financial Services Regulation
Operational resilience, payment rules and supervisory expectations as design inputs.
Geo-Restriction & Sanctions
Blocking access by jurisdiction, and the accuracy and evasion problems that come with it.
Lawful Basis & Purpose Limitation
Why you may hold the data, and why that forbids the second use somebody proposed.
PCI-DSS Scoping
Segmentation and tokenisation to shrink what is in scope, because scope is the cost.
Privacy by Design
Data minimisation, default protection and purpose binding as structural decisions.
Privacy-Enhancing Technologies
Differential privacy, secure enclaves and federated computation, and what each buys.
Pseudonymisation
Separating identity from record, and the re-identification risk that remains.
Records Retention & Legal Hold
Keeping what must be kept, deleting what must go, and freezing both on demand.
Sector Cloud Rules
Regulator expectations for cloud use, exit plans and material outsourcing notification.
Third-Party Risk
Assessing, contracting and monitoring the vendors your architecture now depends on.
Data Architecture
General material on structuring, storing and governing data.
Data Platform Architecture
General material on designing the analytical data estate end to end.
Change Data Capture
Turning a database's replication log into a stream, and its coupling risk.
Client Caching & Data Layer
Stale-while-revalidate, invalidation and optimistic updates on the client.
Data Classification
Knowing which fields are regulated, because every control depends on it.
Data Governance
Ownership, lineage, quality, catalogues and who may see what.
Data Lakes & Lakehouses
Open formats on object storage with transactional metadata on top.
Data Lifecycle & Retention
How long data is kept, where it ages to, and how it is actually deleted.
Data Platform Tenancy
Multiple domains on shared storage and compute, with separable access and cost.
Data Vault Modelling
Hubs, links and satellites, and the auditability and load parallelism they buy.
Data Virtualisation
Querying across sources without moving data, and the performance ceiling that imposes.
Data Warehousing
Dimensional modelling, star schemas and analytical workloads.
Data-Flow Diagrams
Following the data across trust boundaries rather than the calls.
Medallion Architecture
Bronze, silver and gold layers, and what each layer is allowed to guarantee.
Multi-Region Architecture
Surviving a region, and the data consistency price of doing so.
Regulatory Constraints
Non-negotiable requirements that remove design options entirely.
Regulatory & Data Protection Architecture
The obligations that constrain a design before a single quality attribute is discussed.
Data Architecture
Where state lives, how it is modelled, replicated, partitioned and governed.
Data Platform Architecture
The analytical estate: storage layout, ingestion, transformation and the compute that reads it.
AI-Era Architecture
AI workloads meeting security, data, networking, reliability and cost.