-
Notifications
You must be signed in to change notification settings - Fork 2
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
implement aggregate REST flow #4
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When state is needed after a command, check if created event was successfully applied, and eventstore returned a beautiful OK that the event was persisted, so in terms of latency, you have now the most young state created, and instead of round-tripping to eventstore to return to REST, send back the state from the mutated aggregate as an answer, using pipelines.
Below some resources:
http://stackoverflow.com/questions/32476397/how-to-support-command-in-rest-while-doing-rest-cqrs-and-eventsourcing-together
https://lostechies.com/jimmybogard/2016/06/01/cqrs-and-rest-the-perfect-match/
http://stackoverflow.com/questions/32476397/how-to-support-command-in-rest-while-doing-rest-cqrs-and-eventsourcing-together
https://www.infoq.com/articles/rest-api-on-cqrs
https://groups.google.com/forum/#!topic/dddcqrs/YdTAIcGMXFI%5B1-25%5D
http://vvgomes.com/cqrs-and-rest/
The text was updated successfully, but these errors were encountered: