Skip to main content

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.

4
  • 2
    Very good explanation! Commented Mar 30, 2021 at 19:40
  • But ... "if this (koff, koff) old programmer might dare to say," far worse(!) than any "spaghetti code!" Don't design software this way. Your grandchildren will hate you for it. Commented Mar 30, 2021 at 20:04
  • @MikeRobinson :-) I remember having worked with low level event loops, and it was indeed very tricky. Especially as not all the vents were completely independent. But domain events are at a very different level of abstraction. Moreover, in the storming workshop, the events are unrolled to make a chronological perspective that is really easy to understand. I don't think that it's a fatality to have unreadable code with event processing ;-) By the way, some CEP gurus pretend that every company is just an efficient distributed event processing engine. Commented Mar 30, 2021 at 21:24
  • Wow, great answer thank you! So as an example: for every item in an order, a warehouse picker needs to locate and scan that item then load it on a rack. If I needed to model that process but show that it loops, perhaps I could model it once with the šŸ” next to it, then have an event that says "All items picked" or something? Commented Mar 31, 2021 at 23:35