Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Architectural pattern that manages the current state as the result of a sequence of events that are captured and stored and each trigger a state change.
1
vote
How does "event triggers event" really work in Event Sourcing / CQRS?
I would paraphrase your concerns as follows:
A (mostly) one-to-one correspondence between commands and events not only
requires more (boilerplate) code but also seems redundant.
Having the business …
15
votes
In CQRS/ES, can a command create another command?
In retrospect, I think I was complicating the issue.
In general, commands should either throw an exception or raise one or more events.
If I could summarise the architecture of Event Sourcing it wou …