Skip to main content

21.3 Domain & Space Architecture

Datasphere spaces are secure modeling environments. SAP documentation describes acquisition, preparation and modeling as activities performed inside spaces, with data shared or exposed beyond a space through controlled mechanisms.

Domain-oriented pattern​

Example:

Finance | Procurement | Sales | HR | Supply Chain

Each domain can own its acquisition and semantic assets while exposing governed reusable outputs.

Space boundary decisions​

Use a separate space when one or more of these differ materially:

  • ownership
  • security
  • lifecycle
  • source connectivity
  • operational responsibility
  • resource requirements

Do not create a space for every table.

Hub-and-spoke pattern​

A governed foundation can publish reusable dimensions or reference data:

Domain spaces -> governed shared assets -> consumption spaces

Avoid turning the central hub into a giant monolithic warehouse.

Cross-space design​

Cross-space sharing should answer:

  • who owns the source;
  • what is being shared;
  • whether data is read-only;
  • what security follows the asset;
  • what happens when the producer changes it.

Architect exercise​

Design spaces for 12 domains, three security classifications and two major consumer groups. Explain why each boundary exists.