Overview
The module dependency diagram shows the layered dependency structure among BitzOrcas.Modern’s 18 bounded contexts. Modules are arranged in four tiers: Contracts, Business, SaaS Capabilities, and Infrastructure.
Dependencies flow strictly downward. Red lines annotate reverse dependencies or cross-layer references that require special attention.
Key takeaways
- Tenancy is the bottom-layer module; all other modules may depend on its contracts
- Authorization depends on Identity and Tenancy, providing unified permission decisions
- Search and Reporting receive data only through events — they never reverse-depend on business modules
- Architecture tests (ArchUnitNET) enforce these boundaries — violations fail CI
Related
- Modular monolith — module governance deep dive
- Dependency injection — how the composition root assembles modules
- Multitenancy deep dive — tenant resolution chain