Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow messages (command, queries and events) to belong to a domain (without a service) #1173

Open
boyney123 opened this issue Feb 19, 2025 · 3 comments

Comments

@boyney123
Copy link
Collaborator

boyney123 commented Feb 19, 2025

Use Case

Speaking with a few users (@MathiasEurostar) of EventCatalog, they expressed it would be nice to have (mainly events) messages part of their domain.

The way I see this working in that domains could also have a events queries and commands section on the domain (optional ofc), if they are present then the catalog would associate that event to that domain (without a service).

We would have to add functions to getMessagesByDomain which would also have to traverse the services if any are in the service to get their messages too.

Proposed Solution

---
id: Payment
name: Payment
version: 0.0.1
summary: |
  Domain that contains payment related services and messages.
owners:
    - dboyne
events:
  - id: InventoryAdjusted
     version: 1.0.0 
badges:
    - content: Payment Domain
      backgroundColor: blue
      textColor: blue
---

## Overview

The Payment Domain encompasses all services and components related to handling financial transactions within the system. It is responsible for managing payments, transactions, billing, and financial records. The domain ensures secure, reliable, and efficient processing of all payment-related activities

## Bounded context

<NodeGraph />

No response

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.
@boyney123
Copy link
Collaborator Author

Image

Also add events/commands/queries in this view

@boyney123 boyney123 self-assigned this Feb 19, 2025
@boyney123
Copy link
Collaborator Author

Think we should also extend the SDK to support adding events to domains etc.

@carlosallexandre
Copy link
Contributor

Related #1046

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants