Re: Re: Are web applications complex enough to domain-driven design?

Hi,


Good advice. I wrote a small post on my view some years ago:
http://se-thinking.blogspot.se/2011/10/is-domain-driven-design-always.html


In addition, I think that even a CRUD-system benefits from defining the
Ubiquitous Language to make sure naming is correct. Besides, my experience
is that most systems grow in complexity over time...


Jörgen


On 11 September 2014 08:14, [email protected] [domaindrivendesign] <
[email protected]> wrote:


>
>
> Hi
>
> A web app is just a technical platform. A domain driven approach could
> benefit web apps, mobile apps or desktop apps *if* they have complex
> business rules that might change often.
>
> You'll usually see such rules referred to as requirements that says that
> "when X happens in the system, Y should happen as a result", or "When A, B
> and C have finished processing, start process D and E".
>
> In these cases you'd want a trivial mapping between the business
> requirements and your code, so when a change to the requirements comes
> along, you'll know exactly where the software should change, and that's the
> domain model layer.
>
> Udi Dahan lists some of the reasons to (and not to) employ the domain
> model pattern (and thus DDD) and its benefits in this article:
>
> Employing the Domain Model Pattern
> <http://msdn.microsoft.com/en-us/magazine/ee236415.aspx>
>        [image: image]
> <http://msdn.microsoft.com/en-us/magazine/ee236415.aspx>
>      Employing the Domain Model Pattern
> <http://msdn.microsoft.com/en-us/magazine/ee236415.aspx>
>       View on msdn.microsoft.com

> <http://msdn.microsoft.com/en-us/magazine/ee236415.aspx>
>   Preview by Yahoo
>
>
> Cheers,
> Moran
>
>  
>