Comments on: DDD: Only for complex projects? http://www.markhneedham.com/blog/2009/04/06/ddd-only-for-complex-projects/ Thoughts on Software Development Sun, 14 Mar 2010 09:50:28 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Craig Berntson http://www.markhneedham.com/blog/2009/04/06/ddd-only-for-complex-projects/comment-page-1/#comment-13816 Craig Berntson Tue, 07 Apr 2009 21:12:27 +0000 http://www.markhneedham.com/blog/?p=1105#comment-13816 Good post. I'm speaking at DevLink conference in August on the topic, "Domain Driven Design for the Average Application" .. in other words, how to use DDD concepts when the application is not enterprise level nor extremely complex. Good post. I'm speaking at DevLink conference in August on the topic, "Domain Driven Design for the Average Application" .. in other words, how to use DDD concepts when the application is not enterprise level nor extremely complex.

]]> By: Neil http://www.markhneedham.com/blog/2009/04/06/ddd-only-for-complex-projects/comment-page-1/#comment-13776 Neil Tue, 07 Apr 2009 12:32:30 +0000 http://www.markhneedham.com/blog/?p=1105#comment-13776 Great article, I'd have to agree and have found at least trying to create a Ubiquitous Language really helpful for all sizes of project. Perhaps not a strict interpretation of UL but even getting team members to just use the same terminology when discussing aspects of a domain really helps me! - (as well as forcing people to really think about what they're saying). Great article,

I'd have to agree and have found at least trying to create a Ubiquitous Language really helpful for all sizes of project.

Perhaps not a strict interpretation of UL but even getting team members to just use the same terminology when discussing aspects of a domain really helps me! – (as well as forcing people to really think about what they're saying).

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #323 http://www.markhneedham.com/blog/2009/04/06/ddd-only-for-complex-projects/comment-page-1/#comment-13756 Reflective Perspective - Chris Alcock » The Morning Brew #323 Tue, 07 Apr 2009 06:22:02 +0000 http://www.markhneedham.com/blog/?p=1105#comment-13756 [...] DDD: Only for complex projects? - Mark Needham questions the idea that Domain Driven Design is only needed for complex projects with a look at what DDD practices bring to all projects [...] [...] DDD: Only for complex projects? – Mark Needham questions the idea that Domain Driven Design is only needed for complex projects with a look at what DDD practices bring to all projects [...]

]]> By: The Rationalist Manifesto » Blog Archive » DDD = ? http://www.markhneedham.com/blog/2009/04/06/ddd-only-for-complex-projects/comment-page-1/#comment-13741 The Rationalist Manifesto » Blog Archive » DDD = ? Tue, 07 Apr 2009 01:40:41 +0000 http://www.markhneedham.com/blog/?p=1105#comment-13741 [...] Needham has a very interesting post regarding Domain Driven Design. One paragraph that caught my eye especially is: As Luis Abreu [...] [...] Needham has a very interesting post regarding Domain Driven Design. One paragraph that caught my eye especially is: As Luis Abreu [...]

]]> By: DotNetShoutout http://www.markhneedham.com/blog/2009/04/06/ddd-only-for-complex-projects/comment-page-1/#comment-13728 DotNetShoutout Mon, 06 Apr 2009 22:47:57 +0000 http://www.markhneedham.com/blog/?p=1105#comment-13728 <strong>DDD: Only for complex projects? at Mark Needham...</strong> Thank you for submitting this cool story - Trackback from DotNetShoutout... DDD: Only for complex projects? at Mark Needham…

Thank you for submitting this cool story – Trackback from DotNetShoutout…

]]> By: Carlo http://www.markhneedham.com/blog/2009/04/06/ddd-only-for-complex-projects/comment-page-1/#comment-13720 Carlo Mon, 06 Apr 2009 20:35:29 +0000 http://www.markhneedham.com/blog/?p=1105#comment-13720 Hi, good article. I agree with you that DDD concepts can definitely be used in smaller scale projects and I try to use some of the 'patterns' in these types of projects. Typically things like value object, specification, repository, entity aggregate are useful in most projects. The organisational patterns are great to be aware of but more costly in time and effort for most smaller projects and I guess thats the main point that most of those high profile speakers are making. The cost-to-benefit ratio is not great for simpler projects where it's really 'get some info, process it and persist it'. Thats why patterns like 'Active Record' and 'Transactional Script' are in widespread use (that and the fact that most developers regress to procedural code when confronted with tight deadlines :) Hi, good article. I agree with you that DDD concepts can definitely be used in smaller scale projects and I try to use some of the 'patterns' in these types of projects. Typically things like value object, specification, repository, entity aggregate are useful in most projects.
The organisational patterns are great to be aware of but more costly in time and effort for most smaller projects and I guess thats the main point that most of those high profile speakers are making.

The cost-to-benefit ratio is not great for simpler projects where it's really 'get some info, process it and persist it'. Thats why patterns like 'Active Record' and 'Transactional Script' are in widespread use (that and the fact that most developers regress to procedural code when confronted with tight deadlines :)

]]>