Eric Evans talks on domain driven design in this interview. he is briefing on the basics of DDD and particularly on how you should focus on the domain targeted design and not on any underlying technologies. I think it is a common mistake that when we do the domain driven design we tempt to have a particular technology in the back of the mind, which will always disturb our focus.
He talks about the ubiquitous languages which have been used in such designs. The concern I have is, who is the right person to do such domain driven design. Is he the domain driven architect , project leader, tech lead or the pre sales person? And at which point this phase will fall in the process cycle? because we often have the communication gap on the domain driven design when it comes to the development life cycle. So we need to make sure the model and the ubiquitous language are properly conveyed through out the software life cycle.
Another important aspect I found is about on which areas of domain you have to model. Evans says, you should not model everything in the domain. It is very important to isolate the models and only focus on the complicated areas. Obviously overuse of DDD will probably affect the design as well as the business value.
Want to find more .. visit this interesting site on DDD
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment