A
Author #1
Hi, I am new to Domain-Driven Design.
I have spent a few hours reading on the web on this topic, and have
also read the *preface* of Eric Evans' book. But I still have not
figured out what they mean by "domain". A lot of articles quote
Eric's DDD premise as such (e.g.: http://domaindrivendesign.org/resources/what_is_ddd).
<quote>
The premise of domain-driven design is two-fold:
* For most software projects, the primary focus should be on the
domain and domain logic; and
* Complex domain designs should be based on a model.
</quote>
But, they don't tell noobs what they mean by "domain".
Maybe I am just unlucky and haven't found an article that defines
"domain", or maybe authors think that it is common sense and don't
bother defining this terminology.
I guess I will have a better idea if I read the whole book of Eric
Evans, but if any of you could kindly explain briefly what a "Domain"
is before I finish that book, it'll definitely get us noobs up to
speed with this design principle.
I have spent a few hours reading on the web on this topic, and have
also read the *preface* of Eric Evans' book. But I still have not
figured out what they mean by "domain". A lot of articles quote
Eric's DDD premise as such (e.g.: http://domaindrivendesign.org/resources/what_is_ddd).
<quote>
The premise of domain-driven design is two-fold:
* For most software projects, the primary focus should be on the
domain and domain logic; and
* Complex domain designs should be based on a model.
</quote>
But, they don't tell noobs what they mean by "domain".
Maybe I am just unlucky and haven't found an article that defines
"domain", or maybe authors think that it is common sense and don't
bother defining this terminology.
I guess I will have a better idea if I read the whole book of Eric
Evans, but if any of you could kindly explain briefly what a "Domain"
is before I finish that book, it'll definitely get us noobs up to
speed with this design principle.