By pulesen
via techper.net
Published: Nov 29 2008 / 14:13
I really wanna do DDD. But I also got to thinking: “Why, actually?”
The current architectures and approach to design with a services and dao layer many of us have in web-applications using either spring/hibernate or ejbs is "good enough", as in, it gets the job done fine.
So, is the DDD movement mostly an intellectual exercise or does it really matter?
Comments
villane replied ago:
Good post, although I'm not sure I agree that DDD is not going to make us more productive. It may not be more productive when developing a green field system, but I have recently been maintaining, refactoring and adding new features to a telco's systems which have barely even a smell of domain driven design, even not good OOD -- much of the code is procedural, although it is properly divided into layers very similarly to most enterprise java systems. I have never been less productive than when maintaining this system and I'm fairly certain that if the system was designed with DDD in mind, the maintenance costs could be several times less.
mknutty replied ago:
Most "productivity" claims ignore the whole lifecycle.
Voters For This Link (12)
Voters Against This Link (3)