Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve been doing some reading on Domain Driven Development but can’t see how this would really change any development practices, besides maybe keeping our domain object names insync with elements in our requirement documents.
For those really into DDD, how has this change your development pracitces?
The thing I found about DDD is that it merely gives names to the concepts and principles I used already. To be useful it does not have to change the way we develop systems, it can just provide us with the terminology to discuss our approach.
The few things that changed for me after reading Domain Driven Design Quickly are:
I now identify aggregare roots, entities and value types.
I have embraced the repository pattern along with nHibernate for implementing the persistence layer. (This is because this ORM feels like a good fit to me when implementing aggregate boundaries)
I embrace the use of an ubiquitous language, you elude to (probably the most important change I made).
Other than that, DDD has merely formalised what I thought of as common sense.