1

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?

2

Re: It is amazed by beauty CQRS and Event Sourcing

Arpanx;
https://blogs.msdn.microsoft.com/cesard … in-events/

3

Re: It is amazed by beauty CQRS and Event Sourcing

Subtracted here
http://cqrs.nu/Faq
Can an aggregate send an event to another aggregate?
No.
Should a command handler affect one or several aggregates? (Though at me "event handler")
Only one.
All right, I understood that understood nothing. I will go to read further. But a subject very abrupt, it is necessary to drive only

4

Re: It is amazed by beauty CQRS and Event Sourcing

Arpanx wrote:

Now I want that "Domen2" learned about event, I so understand in "EventHandler1" I should send to the bus a command "Update2"

No. Events do not provoke change of other aggregates.

Arpanx wrote:

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.

No, is not present and once again is not present. Event is result command performance. Any changes are executed only through commands. Event cannot lead to start of new commands.

Arpanx wrote:

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?

It is not necessary to "kick" other domain.
If it is interesting, give a specific case, we will understand.

5

Re: It is amazed by beauty CQRS and Event Sourcing

Arpanx wrote:

Literary trash it was certainly added

There where "literary trash", beauty only for the sake of beauty is added.

Arpanx wrote:

but it is felt that it relieves of a headache in the future.

These are five.

6

Re: It is amazed by beauty CQRS and Event Sourcing

behind a board wrote:

it is passed...
There where "literary trash", beauty only for the sake of beauty is added.

Not the difficult and expensive technics is necessary to all to hammer together a box.

7

Re: It is amazed by beauty CQRS and Event Sourcing

hVostt wrote:

Not the difficult and expensive technics is necessary to all to hammer together a box.

When "it is amazed by beauty" blondes, it is necessary to know that blondes have lacks)).

8

Re: It is amazed by beauty CQRS and Event Sourcing

skyANA, thanks for the link, did not see earlier this selection.
Simply I look in different examples on a miscellaneous it it is implemented. Where through IoC, where the mechanism Subscribe
It is necessary - it is not necessary, then I will understand. Now at least learns the dog I will build on this infrastructure.
Simply still impressions are fresh when on FrontEnd (TypeScript) passed to the system of sending Event and Bus as at once it became easier to live. Tell-Don't-Ask the approach too it to be pleasant. Simply saw enough already of a hell from 1000 Utils and Helper classes.
People pass with Orakla and Java to "new technologies" from MS and think that S solves all their problems. But I feel that it is necessary to change the approach.

9

Re: It is amazed by beauty CQRS and Event Sourcing

Arpanx wrote:

Simply impressions still are fresh when on FrontEnd (TypeScript) passed to the system

then certainly.
and front often with a different paradigm and thinking.

10

Re: It is amazed by beauty CQRS and Event Sourcing

Arpanx wrote:

People pass with Orakla and Java to "new technologies" from MS and think that S solves all their problems.

where the such? Would not hear that who that refused from  in favor of a msec

Arpanx wrote:

But I feel that it is necessary to change the approach.

To try that that new  business useful

11

Re: It is amazed by beauty CQRS and Event Sourcing

handmadeFromRu wrote:

  where the such? Would not hear that who that refused from  in favor of a msec

Heard, saw. And reverse too saw. In both cases "yes that for  in XXX it was in normal way, and here in YYY through":-D

12

Re: It is amazed by beauty CQRS and Event Sourcing

hVostt;
))) +1. Insignificant talks

13

Re: It is amazed by beauty CQRS and Event Sourcing

hVostt wrote:

Heard, saw. And reverse too saw. In both cases "yes that for  in XXX it was in normal way, and here in YYY through":-D

And the reasons of such manoeuvres? Well I would understand there passage with  on   heaps of buns thus there  the general on .

14

Re: It is amazed by beauty CQRS and Event Sourcing

My colleagues looked on Android Architecture Components, tried, were spat.
For two days  Redux under Android also began like mad  therefore as it is simple, clear and convenient.

15

Re: It is amazed by beauty CQRS and Event Sourcing

handmadeFromRu wrote:

it is passed...
And the reasons of such manoeuvres? Well I would understand there passage with  on   heaps of buns thus there  the general on .

Normally reason, this sentence of operation with suitable level . Well personally I on Java would not leave that the stack.NET is pleasant to me more, and experience is saved already up much which was to be merged no.

16

Re: It is amazed by beauty CQRS and Event Sourcing

skyANA;
Still tell on Kotlin:-D

17

Re: It is amazed by beauty CQRS and Event Sourcing

hVostt wrote:

skyANA;
Still tell on Kotlin:-D

Also I will tell: on Kotlin:-Q

18

Re: It is amazed by beauty CQRS and Event Sourcing

handmadeFromRu wrote:

it is passed...
And the reasons of such manoeuvres? Well I would understand there passage with  on   heaps of buns thus there  the general on .

Speech about the developer, instead of the companies smile

19

Re: It is amazed by beauty CQRS and Event Sourcing

And I am not amazed. Any  the methodology, for strongly loaded systems, probably, is adequate. I do not have in it need. Can then will, when already on cats experiments deliver all. And I again will be late

20

Re: It is amazed by beauty CQRS and Event Sourcing

Though at me requests from commands are separated. The reason:
Commands - over objects, well approaches , to that-that here not  passage from the OOP world in the world of storages (well, at me C# as at others I do not know. I think - in  languages also/is similar)
Requests - permanently become complicated,  overindulgence in linq, and then without  SQL not to manage

21

Re: It is amazed by beauty CQRS and Event Sourcing

Arpanx wrote:

It is amazed by beauty CQRS and Event Sourcing. Literary trash it was certainly added

In nonsense be engaged means

22

Re: It is amazed by beauty CQRS and Event Sourcing

love_bach wrote:

and I am not amazed. Any  the methodology, for strongly loaded systems, probably, is adequate. I do not have in it need. Can then will, when already on cats experiments deliver all. And I again will be late

Strongly loaded systems and without CQRS wrote. It is applicable widely enough. Who not in smoked, and does not wish to study, can transit by that could master, and not brawl.

23

Re: It is amazed by beauty CQRS and Event Sourcing

love_bach wrote:

it is passed...
In nonsense be engaged means

The next nonsense carry, here that means.

24

Re: It is amazed by beauty CQRS and Event Sourcing

hVostt wrote:

it is passed...
The next nonsense carry, here that means.

Well and what not so

25

Re: It is amazed by beauty CQRS and Event Sourcing

love_bach wrote:

it is passed...
Well and what not so

And what so? To write it is a lot of and to think is   much?