Skip to main content

21.11 Multi-Tenant & Environment Architecture

Enterprise landscapes usually need lifecycle isolation in addition to logical domain isolation.

Environment pattern​

DEV -> TEST/QA -> UAT -> PROD

Not every organization needs every stage, but production changes should be controlled independently from development.

Tenant versus space​

Use tenants for stronger lifecycle, operational or organizational isolation.

Use spaces for modeling, ownership, security and resource boundaries within a tenant.

Multi-tenant questions​

Consider:

  • regulatory isolation
  • business-unit autonomy
  • release independence
  • capacity isolation
  • network/connectivity differences
  • operating ownership
  • cost allocation

Global versus regional architecture​

A global enterprise may use:

Global standards -> regional/domain implementation -> local consumption

Avoid centralizing every object if regional autonomy is a real business requirement.

Architect trade-off​

More tenants increase isolation and operational overhead.

More spaces increase logical organization but do not replace all tenant-level lifecycle concerns.

Choose the minimum topology that satisfies the actual constraints.