Topic: It is amazed by beauty CQRS and Event Sourcing
It is amazed by beauty CQRS and Event Sourcing. Literary trash it was certainly added, but it is felt that it relieves of a headache in the future.
In a head certainly porridge, experts so to think was not, I am afraid straight off I will break Single responsibility principle.
Question, whether is normal so to do.
Is at us "Domen1", the command on the bus (BUS) "Update1" came, executed this command, sent in bus "Event1" (type "Domen1 has been updated")
In the same domain at us is "EventHandler1" it is all as though responsibility of one domain.
Now I want that "Domen2" learned about event, I so understand in "EventHandler1" I should send to the bus a command "Update2"
The assumption: "Domen2" itself subscribe for bus BUS cannot. (It after all lies in basis EF) and he to listen to the bus cannot in any way.
It turns out I want in "EventHandler1" to send a command "Update2", but I turn out in "1", should know about "a command 2"
Somehow it is not beautiful. But specific copies of domains sleep in basis, they cannot sign.
How to kick other domain? Whether which I described a normal method?