Is it correct to handle the event in an aggregate published from another aggregate? Or should a domain only process commands?
In my case, I have an application that controls the settings. I have an aggregate for an application and an aggregate for a group of applications. When I want to create settings for a specific application group, then the command is processed by my application group, then the application group publishes the GroupSettingsCreated event, but DDD says that we can process this event directly in my ApplicationAggregate? Or should I handle this event in an event handler, match it in a command, and send it to my ApplicationAggregate?
thanks
John
source share