Presumably we could resurrect state by applying the same set of commands, so why not simply store commands rather than events?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Presumably we could resurrect state by applying the same set of commands, so why not simply store commands rather than events?
Events, communicate “this happened in our system”. Events occur when a command has been accepted and processed. No one can reject or change the fact that it happened. It’s the only authoritative source of changes in the system
Commands are just a way for a part of the system (like a UI) to tell the component in charge of making changes to the system (the “command handler”) what it wants done. However, the command handler can choose not to process the command for various reasons. The UI could have stale information and processing the command wouldn’t make business sense or the user could have not had the privileges to perform that action. Either way, the command is really just a request & have no bearing on the state of a system
.