DDD: skip the tech bits
I would like to share some thinking on Domain Driven Design.
The amazing value provided by Domain Driven Design is the focus on the business side of the Software.
This same focus brings a constraint to your software development process: IN-DEPTH Business Knowledge becomes a MUST HAVE.
I just want to make sure you will remember this constraint when planning to apply DDD.
If you have any sort of problem on the matter of handling this constraint, take my advice: Stay with the CRUD based option.
Domain Driven Design can absolutely improve what you are going to deliver to your customer.
But don’t expect all you have to do is having stuff that you call “Aggregate Root”, “Domain Model”, or “Repository”.
Good points Rafael.
In any case, in-depth business knowledge is a very important skill to be developed, with or without DDD. From my experience this is what differentiates the irreplaceable from the replaceable members of a team.
Rodrigo Vieira
21 Dec 09 at 10:15
Rodrigo,
I agree that deep business knowledge is always important.
But I would tell that Domain Driven Design will require an even more solid understanding of the domain, in order to fulfill the requirement of an ubiquitous language and the usage of such language at the code level.
Does that make sense?
rafanoronha
21 Dec 09 at 13:58