-
-
Notifications
You must be signed in to change notification settings - Fork 236
Description
Use Case
We just started with event catalog and are active in education having a student information service that delivers 50+ events/messages (academic structure, personal student information, student financing). Works great but the diagrams on domain level or at service level are now bloated with all the messages/events.
Proposed Solution
Lets say we have a Student information service that sends lots of messages/events but we can group/categorize the events/messages in a certain context (academic structure, student personal information, ...) which could be used visually to have "Student information service" (producer) => Academic structure messages + student personal information messages => CRM service (consumer). An end user could open up (zoom in on) the group/context of academic structure messages and you would then see "Student information service" (producer) => Program created event / Program updated event / ... => CRM service (consumer)
This would keep domain / service overview more usable while still offering a deep dive towards the events/messages in combination with focus mode if you would search for an event.
Implementation Notes
Adding categories/group names/tags on events
Making the categories/group names/tags usable in charts of domains / services when a large amount of messages occurs (10+ ?)
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.

