-
Notifications
You must be signed in to change notification settings - Fork 26
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
integration questions #135
Comments
This is usually the easier path to take. A separate module that only contains your message definitions and is imported into your orchestrator and services. This way your dependencies will stay loosely coupled, whilst still allowing any service to publish/subscribe to any message. |
Fantastic! thank you very much for the quick reply! I'll try and contribute an article with a concrete implementation. |
i'm building a simple system consisting of an orchestrator and three microservices.
should I define event classes in each service? or should I create an npm module with all message (commands / events) definitions?
I'm thinking something like this
Would this implementation be correct? Is there any example of a different and better way?
The text was updated successfully, but these errors were encountered: