Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • @DocBrown one issue is lack of concern separation. Commented Mar 11, 2020 at 9:01
  • @Basilevs: separation of concerns is not an end in itself, it is a means to an end. And I was asking the OP which real issues they are facing for this specific situation. Commented Mar 11, 2020 at 9:08
  • 1
    @DocBrown The problem is the build process. I have both packages (com.example.sales and com.example.billing) in separate Maven artifacts. But those has dependencies to each other, so it is impossible to build them. Commented Mar 11, 2020 at 9:34
  • @DocBrown Thank you, I tried to collaborate more about the problem in the answer. Commented Mar 11, 2020 at 10:41
  • Make it as they where written in different languages. You could not share libs so basically you would re-write events for each boundary. Wouldn't you? Bear in mind that there's no DRY breaking in duplicating events here and there. They gather no knowledge that worth reuse. These are somewhat like messages. Commented Mar 13, 2020 at 10:31