Timeline for How to resolve cyclic dependencies in Event-driven systems?
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2024 at 3:49 | answer | added | user453500 | timeline score: 1 | |
| Nov 7, 2021 at 15:00 | history | tweeted | twitter.com/StackSoftEng/status/1457362203452006402 | ||
| Nov 7, 2021 at 14:45 | answer | added | Connell♦ | timeline score: 0 | |
| Mar 13, 2020 at 10:31 | comment | added | Laiv | 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. | |
| Mar 13, 2020 at 6:46 | answer | added | Nils | timeline score: 0 | |
| Mar 11, 2020 at 15:20 | answer | added | Mike Robinson | timeline score: 0 | |
| Mar 11, 2020 at 10:50 | answer | added | ttulka | timeline score: 2 | |
| Mar 11, 2020 at 10:43 | answer | added | Doc Brown | timeline score: 8 | |
| Mar 11, 2020 at 10:41 | comment | added | Barney | @DocBrown Thank you, I tried to collaborate more about the problem in the answer. | |
| Mar 11, 2020 at 10:40 | history | edited | Barney | CC BY-SA 4.0 |
the problem explained
|
| Mar 11, 2020 at 9:34 | comment | added | Barney | @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. | |
| Mar 11, 2020 at 9:08 | comment | added | Doc Brown | @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. | |
| Mar 11, 2020 at 9:01 | comment | added | Basilevs | @DocBrown one issue is lack of concern separation. | |
| Mar 11, 2020 at 8:37 | history | asked | Barney | CC BY-SA 4.0 |