This group is for discussion of the domain-driven style of designing software, and the book by Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Business Software. Questions and discussion of the book content is welcome here, as well as sharing of experiences applying DDD, and discussions of the topic in general.
Interesting idea to use Value Objects for names. I have decided to use VOs for E-mail, social security number and others, but I haven't considered using it for
Jeremie, The question I ask is why such preference considering how traditionally double dispatch and strategy patterns are used? Just note that Repositories
Hey, not entirely sure if it's appropriate to post here – i looked for a faq for some policy, but i'll word my request informally. My company in Ottawa is
But the shortcut you are taking to write less code doesn't prove that the repository *should* be responsible for testing unicity when creating/modifying
Oh, Ok. I understand now. ... That is a design only constraint indeed. Nevertheless the subject is a domain object as such the rule IMHO should be kickoff by