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*

3
  • 2
    You really can't generalise. It MIGHT be. It might be not. Does it matter? IMHO no, especially early DDD talks forgot to think that reality is different and for example, ORMs/languages/frameworks dictate some rules (and the price to circumvent them may be too high or not worthy). Ok, also project you listed don't seem to be best possible .NET code ever... Commented Jun 10, 2018 at 18:51
  • @Adriano Repetti, do you know of any good cqrs open source projects? Do you put validation in your commands? Commented Jun 10, 2018 at 19:06
  • 2
    I'd distinguish parameters validation from domain validation (when applicable). For example a null parameter has nothing to do with the domain, it comes from an implementation detail (language you're using). The former I always do, no matters what and where. Domain validation is more tricky but if you really really worry about broken invariants then, IMO, you should consider immutable objects. They're (again just in my opinion) an, often, better tradeoff than a holy war against languages we really use (and that was a critique to many older DDD takes) Commented Jun 10, 2018 at 21:58