Use Case

We have several hundred domains, and so the need for nesting subdomains is critical for us to organize them all. We currently have 3 levels, you can think of the top level to be something akin to a Division in a large company, the second level is functional area, and the third level is the actual feature domain where the bounded contexts live.

#1690
#1712

https://ddd-practitioners.com/2023/03/07/the-difference-between-domains-subdomains-and-bounded-contexts/
https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-decomposing-monoliths/decompose-subdomain.html

Proposed Solution

It would make navigation so much easier if there was a way to categorize/group the various domains, services, resources, entities, etc. to a more granular level. Maybe there is a way to simply categorize the leaf domains and not even bother with the notion of subdomains?

Implementation Notes

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.
• If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out in the EventCatalog Discord.