Data residency
Data residency is a requirement or practice governing the geographic locations or jurisdictions in which data may be stored or processed.
Architecting an Apache Iceberg Lakehouse
Data residency is the requirement that data be stored or processed within specified geographic or jurisdictional boundaries.
- How it is used
- Constrains lakehouse storage, catalog, and query architecture when organizations must satisfy geographic, privacy, or regulatory boundaries.
- How deep it goes
- Explains placement, replication, encryption, auditing, and query enforcement, but stops short of specifying one universal deployment pattern.
- Examples
- Uses regional healthcare datasets, jurisdiction-aware Iceberg tables, and hybrid bank storage spanning cloud and on-premises object stores.
- What you can do after
- Operate/configure storage, catalogs, and query paths so regulated data remains localized and compliance evidence remains auditable.
Read how Architecting an Apache Iceberg Lakehouse explains data residency →
MongoDB 8.0 in Action, Third Edition
A data residency policy specifies the geographic locations in which data may be stored or processed.
- How it is used
- Guides Atlas deployment choices when applications require regional data locality, regulatory compliance, low latency, or high availability.
- How deep it goes
- Explains geopartitioning, zones, region roles, and customer configuration, but does not provide command-level setup instructions.
- Examples
- Uses Atlas Global Clusters, regional shards, and Highest Priority, Electable, and Read-only region assignments as implementation examples.
- What you can do after
- Configure Atlas Global Clusters to keep data in designated regions while supporting regional reads, writes, and failover.
Read how MongoDB 8.0 in Action, Third Edition explains data residency →
LLM Customization and Fine-Tuning
A requirement that data be stored or processed within specified geographic or organizational boundaries.
- How it is used
- Uses residency constraints to decide where a model runs, separately from which adaptation technique to choose.
- How deep it goes
- Distinguishes deployment-location controls from adaptation and names regional hosting and self-hosting options.
- Examples
- Uses hospital patient data and regional hosting from Azure OpenAI, Amazon Bedrock, and Google Vertex AI as examples.
- What you can do after
- Operate/configure deployment by choosing a managed regional tenant or self-hosting within the required boundary.
Read how LLM Customization and Fine-Tuning explains data residency →
Also covered in
What to know first
- GDPRThe General Data Protection Regulation (GDPR) is a European Union regulation governing the processing and protection of personal data and establishing related rights for individuals.
- authorizationAuthorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.
- availabilityAvailability is the degree or proportion of time that a system or service is operational and accessible when required.
- HIPAAHIPAA is a United States federal law establishing requirements for the privacy, security, and handling of protected health information and related healthcare transactions.
Related concepts
- runneruses · A runner is a machine or execution environment that runs the jobs or steps of an automated workflow, build, or pipeline.
- privacycontrasts with · Privacy is the protection of information about people or other sensitive subjects from inappropriate collection, access, use, or disclosure, including control over how it is handled.
- GDPRincludes · The General Data Protection Regulation (GDPR) is a European Union regulation governing the processing and protection of personal data and establishing related rights for individuals.
- lakehouse catalogconfigured by · A catalog is a service or interface that registers lakehouse tables, resolves their metadata, and coordinates table updates across data engines.
Questions about data residency
What is data residency?
Data residency is a requirement or practice governing the geographic locations or jurisdictions in which data may be stored or processed.
Which Manning books explain data residency?
Architecting an Apache Iceberg Lakehouse, MongoDB 8.0 in Action, Third Edition and LLM Customization and Fine-Tuning.
What should I know before learning data residency?
Manning books that teach data residency usually introduce GDPR, authorization, availability and HIPAA first.
What is the difference between data residency and privacy?
Data residency is a requirement or practice governing the geographic locations or jurisdictions in which data may be stored or processed. Privacy is the protection of information about people or other sensitive subjects from inappropriate collection, access, use, or disclosure, including control over how it is handled.
What kinds of data residency are there?
Kinds of data residency include GDPR.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.


