CRUD forms are inevitable.
We may have
1. Whole CRUD application with some Challenging FORM
2. Whole Complex Domain Application with some CRUD FORMS
1. Whole CRUD application with some Challenging FORM
The whole application is CRUD
Sub domain is CRUD oriented
As the application grows, there are changes that
Anemic Domain Model ==> Rich Domain Model.
Therefore we will always use the Domain Model pattern
2. Whole Complex Domain Application with some CRUD FORMS
We cannot stop CRUD forms to the part of Complex Sub Domain of Application.
Application may be mix of CRUD forms and Complex Forms
We may have
1. Whole CRUD application with some Challenging FORM
2. Whole Complex Domain Application with some CRUD FORMS
1. Whole CRUD application with some Challenging FORM
The whole application is CRUD
Sub domain is CRUD oriented
As the application grows, there are changes that
Anemic Domain Model ==> Rich Domain Model.
Therefore we will always use the Domain Model pattern
2. Whole Complex Domain Application with some CRUD FORMS
We cannot stop CRUD forms to the part of Complex Sub Domain of Application.
Application may be mix of CRUD forms and Complex Forms
Usually Small and Medium Level Web Applications combination of both. In such situations too we use the Domain Model.
Some Classes are Anemic just bags of getters and setters properties.
Some Classes are Rich and contain Domain Rules.
Some Classes are Anemic just bags of getters and setters properties.
Some Classes are Rich and contain Domain Rules.
Therefore we will always use the Domain Model pattern
No comments:
Post a Comment