We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Implementing subscriptions is a necessary step to properly implement CQRS.
If we adhere to all CQRS best practices, executing a mutation (command) should not return a value (see e.g. https://en.wikipedia.org/wiki/Command%E2%80%93query_separation). Instead the view (query) should be updated after receiving an event.
The flow we try to achieve is something like: mutation -> create event -> update stores -> inform subscribers
mutation -> create event -> update stores -> inform subscribers
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Implementing subscriptions is a necessary step to properly implement CQRS.
If we adhere to all CQRS best practices, executing a mutation (command) should not return a value (see e.g. https://en.wikipedia.org/wiki/Command%E2%80%93query_separation). Instead the view (query) should be updated after receiving an event.
The flow we try to achieve is something like:
mutation -> create event -> update stores -> inform subscribers
The text was updated successfully, but these errors were encountered: