20.3 DEV, TEST & PROD Architecture
A serious Datasphere landscape separates change creation from production operation.
Reference topology
Developer -> DEV -> TEST -> PROD
Optional enterprise stages:
DEV -> INT -> QA -> UAT -> PROD
DEV
Purpose: rapid design and controlled experimentation.
Characteristics:
- model development
- source connectivity for development
- developer-level diagnostics
- synthetic or limited test data where appropriate
TEST / QA
Purpose: integration and non-functional validation.
Validate:
- dependencies
- security
- data quality
- performance
- scheduling
- failure recovery
PROD
Purpose: stable business service.
Protect it with:
- restricted authoring
- controlled transports
- production monitoring
- incident procedures
- change windows where required
Tenant strategy
Separate tenants when isolation, lifecycle independence, security, or operational risk justifies it. Do not create environments merely because three environments are conventional.
Space strategy
Within a tenant, spaces can represent domains, teams, security boundaries or platform responsibilities. Avoid using spaces as a substitute for tenant-level lifecycle isolation.
Architect decision
Choose tenant and space boundaries from four drivers:
Security + Lifecycle + Ownership + Scale
Document why each boundary exists.