Guided Lesson: VForce Lakehouse Fundamentals

4. Governance & Multi-Tenancy

Isolated, traceable, reproducible

Governance is how a data platform stays trustworthy: keeping each customer's data separate, tracking where every value came from, and controlling who can see or change it.

Key terms

Namespace

A named container for tables, much like a folder. VForce Lakehouse gives each tenant its own top-level namespace (for example tenant_demo), so their data is separated by design.

Multi-tenancy

One shared platform serving many separate customers, called tenants, while keeping each tenant's data fully isolated from every other tenant.

Tenant isolation

The rule that one tenant can never read or affect another tenant's data. Here it is enforced at the namespace root, so isolation is structural rather than just a setting.

Lineage

A traceable record of where each piece of data came from and how it was transformed, so any number in a gold table can be followed all the way back to the raw records that produced it.

Governance

The controls around who may read or change data and how those actions are tracked, so the platform stays auditable and compliant.

Cloud-agnostic

Because the foundation is open files and open table formats, the same lakehouse runs on Azure, AWS, or Google Cloud storage with no proprietary lock-in.