What makes my code DDD (domain-driven design) qualified?

Posted by oykuo on Stack Overflow See other posts from Stack Overflow or by oykuo
Published on 2010-05-25T19:04:51Z Indexed on 2010/05/25 19:21 UTC
Read the original article Hit count: 157

Hi All,

I'm new to DDD and am thinking about using this design technique in my project.

However, what strikes me about DDD is that how basic the idea is. Unlike other design techniques such as MVC and TDD, it doesn't seems to contain any ground breaking ideas.

For example, I'm sure some of you will have the same feeling that the idea of root aggregates and repositories are nothing new because when you are was writing MVC web applications you have to have one single master object (i.e. the root aggregate) that contain other minor objects (i.e. value objects and entities) in the model layer in order to send data to a strongly typed view.

To me, the only new idea in DDD is probably the

  • "Smart" entities (i.e. you are supposed to have business rules on root aggregates)
  • Separation between value object, root aggregate and entities.

Can anyone tell me if I have missed out anything here? If that's all there is to DDD, if I update one of my existing MVC application with the above 2 new ideas, can I claim it's an TDD, MVC and DDD applcation?

© Stack Overflow or respective owner

Related posts about design

Related posts about architecture