Dependency Map¶
This document shows the foundational services almost everything depends on, so sequencing respects real constraints. It complements the bounded-context map.
Foundational Dependencies¶
flowchart TB
Tenant[Tenant Management]
Identity[Identity and Access]
Meta[SaaS Core Metadata]
Config[Config and Flags]
Audit[Audit and Compliance]
Obs[Observability and SRE]
Notif[Notifications]
Billing[Billing]
API[API and Integration]
Consumers[All horizontals and verticals]
Identity --> Consumers
Tenant --> Consumers
Meta --> Consumers
Config --> Consumers
Audit --> Consumers
Obs --> Consumers
Notif --> Consumers
Billing --> Consumers
API --> Consumers
Tenant --> Meta
Identity --> Tenant
Config --> Meta
Billing --> Meta
Hold "Alt" / "Option" to enable pan & zoom
Dependency Rules¶
- Nothing ships before Identity, Tenant, and Config (Tier 0).
- Billing, Notifications, Audit (Tier 1) are required before monetized or regulated products.
- API & Integration is required before connectors and external integrations.
- No shared databases - dependencies are satisfied via APIs and events only.
Common Consumption Patterns¶
| Consumer | Depends on |
|---|---|
| Any vertical product | Identity, Tenant, Config, Billing, Notifications, Audit, Documents |
| Any connector | API & Integration, credential vault, Identity |
| Any AI agent | AI Orchestration, Data, Identity, Audit |
| Any marketplace listing | Marketplace, Billing, Identity, Audit |