Overview
The module ownership map shows how the Platform module’s 13+ bounded contexts are grouped by domain responsibility. Each bounded context owns its domain, application, and infrastructure layers — following the vertical slice pattern.
Key takeaways
- Identity & Access is the largest group — authentication, authorization, users, and roles
- Communication spans three bounded contexts — notifications, chat, and server-sent events
- Each bounded context is independently deployable within the modular monolith
- Cross-context communication uses integration events via CAP Outbox
Related
- Module Internal Structure — vertical slice within each context
- Modules overview — all Platform module bounded contexts