liveBook · Manning

Data sovereignty

Data sovereignty is the principle that data is subject to the laws and governance requirements of the jurisdictions where it is collected, stored, or processed.

How 3 Manning books explain it

Kafka for Architects

Data sovereignty is the requirement that data be subject to the laws and jurisdiction of the geographic location where it is stored or processed.

How it is used
Guides Kafka deployment choices when regulation constrains where data, metadata, and logs may reside.
How deep it goes
Explains jurisdictional requirements, cloud risks, and deployment trade-offs without detailing implementation procedures.
Examples
Uses finance, healthcare, and government workloads alongside regional, private-cloud, on-premises, and hybrid deployments.
What you can do after
Evaluate Kafka deployment models against geographic data restrictions and operational trade-offs.

Read how Kafka for Architects explains data sovereignty →

LLM Customization and Fine-Tuning

The control of sensitive data within an organization's own infrastructure or jurisdiction so it does not leave the trusted boundary.

How it is used
Frames data sovereignty as a compliance constraint that shapes whether sensitive workloads can use third-party APIs.
How deep it goes
Distinguishes deployment-location controls from adaptation and names hosting options, without detailing configuration.
Examples
Uses self-hosted Qwen3-4B with retrieval and regional managed-cloud inference as deployment examples.
What you can do after
Evaluate whether in-boundary deployment is necessary and whether adaptation can make its permitted model capable enough.

Read how LLM Customization and Fine-Tuning explains data sovereignty →

Architecting an Apache Iceberg Lakehouse

Data sovereignty is the principle that data is subject to the laws and governance requirements of the jurisdiction where it is stored or processed.

How it is used
Guides lakehouse catalog and storage architecture where jurisdictional controls constrain deployment and data access.
How deep it goes
Explains federated catalog responsibilities and synchronization requirements, but stops short of implementation procedures or configuration details.
Examples
Uses Dell ECS, AWS GovCloud, Azure Government, Ceph, and MinIO as sovereignty-oriented storage and deployment examples.
What you can do after
Operate/configure a sovereignty-aware lakehouse by separating local catalog control from enterprise-wide discovery and access.

Read how Architecting an Apache Iceberg Lakehouse explains data sovereignty →

Also covered in

Related concepts

Questions about data sovereignty

What is data sovereignty?

Data sovereignty is the principle that data is subject to the laws and governance requirements of the jurisdictions where it is collected, stored, or processed.

Which Manning books explain data sovereignty?

Kafka for Architects, LLM Customization and Fine-Tuning and Architecting an Apache Iceberg Lakehouse.

What is the difference between data sovereignty and data privacy law?

Data sovereignty is the principle that data is subject to the laws and governance requirements of the jurisdictions where it is collected, stored, or processed. A data privacy law is a legal rule governing the collection, processing, storage, disclosure, or transfer of personal data.

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.