If you are using a Domino Nexus deployment, some features depend on data locality, supported through data planes. Data might only be available in certain data planes due to geographic access restrictions or the cost of moving data between data centers.
Data planes are attached to hardware tiers. Depending on the data you need, you must select a hardware tier with the correct data plane when you create a job, workspace, or compute cluster.
Your Domino admin configures the data planes and hardware tiers. They also associate external data volumes (EDVs) with data planes.
EDVs are the primary method for accessing large data sets in Domino Nexus; they have a first-class notion of data locality.
There are two kinds of data planes: local and remote.
The local data plane is a namespace within the same Kubernetes cluster as the Domino control plane (often called the
A remote data plane is a namespace residing within a separate Kubernetes cluster from the control plane.
Some features are only available in the
Local data plane (hosted in the control plane):
Starburst-powered data sources
Other types of data sources can be accessed on both the
Local and remote data planes, but functionality on remote data planes is in Preview.
You can launch jobs and workspaces on a specific data plane by selecting a hardware tier that is configured with that data plane. You can also mount EDVs that are configured for specific data planes, and launch compute clusters alongside your executions.
Localdata plane to use Model APIs, apps, datasets, or Trino data sources in your execution.
You can use a local or remote data plane if you do not need those features.