This is one thing that has been looking for me for a while about DDD. I can clearly see the advantages of the approach when working with non-technical business domains with complex models and a lot of the interaction required between technical experts and non-technical experts in the field.
However, what about the fact that the "domain" in question is technical?
For example, situation A) starts a web start. Imagine that they are trying to accomplish something rather complicated (say, a facebook clone), but almost all employees are technical (or at least have a strong technical understanding).
How about a situation B) A similar situation, but with a slightly less ambitious project and a lonely developer trying to create something with an elegant architecture.
I would be very interested to hear what people have to say. What I'm really trying to get to the meat is where the advantages of DDD lie, what the disadvantages may be, and at what point one outweighs the other ...
source
share