This question already has an answer here:

When we have a system which utilizes Domain Events, it can be quite hard to comprehend the whole workflow (sequence of events) of processing a particular command: how many active handlers we have, how many other events they give raise to, and so on.

On the other hand procedural workflow of Transaction Script is much easier to follow in code. In our team this argument carries much weight, and that's why straightforward Transaction Script is in favor.

I am looking for any approaches that might help eliminate this shortcoming of the Domain Events design pattern.

marked as duplicate by Pavel Voronin, durron597, user22815, user53019, user40980 Jul 30 '15 at 1:21

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 1
    Since "comprehensible" can be vague and subjective, I tried editing your question title to what I believe is the significantly more specific question you're trying to ask. Feel free to revert if I got it wrong. – Ixrec Jul 25 '15 at 20:58