In other words, you should avoid using a model aimed at simplifying a domain model if you don't have one? Sounds fair... The canonical description of the domai

In other words, you should avoid using a model aimed at simplifying a domain model if you don't have one? Sounds fair... The canonical description of the domain model pattern (from Fowler, also) calls for it be _considered_ in a case where there are "complex and ever-changing business rules". He goes on say that "if all you have is some sums and null checks, a different transaction processing pattern is more appropriate". I have seen a lot of event sourced systems, and the vast majority which fail fall into the "not null checks and trivial sums" case rather than the former.