Do MVC web frameworks favor anemic domain model in order to avoid duplication?
Binding directly the form to your model helps a lot to get rid of boiler plate code, but that means that your model must have a getter/setter for each property otherwise it wouldn’t be possible. Another choice would be to create another layer (DTO) only to carry the data to/from the form and then you can have a rich domain model not necessarily with getter/setter for each attribute but that means duplication of fields and validation code.
Does an in-code enumeration provide a stronger domain model than a static table?
Does an in-code enumeration provide a stronger domain model than a static database table?
Does an in-code enumeration provide a stronger domain model than a static table?
Does an in-code enumeration provide a stronger domain model than a static database table?
Does an in-code enumeration provide a stronger domain model than a static table?
Does an in-code enumeration provide a stronger domain model than a static database table?
Does an in-code enumeration provide a stronger domain model than a static table?
Does an in-code enumeration provide a stronger domain model than a static database table?
Validation and data persistence in a domain model
My (first and current) workplace (a .NET shop) suffers from an over-abundance of anemic domain models, to the extent that I don’t really know how validation and data persistence should be handled in a proper domain model.
Validation and data persistence in a domain model
My (first and current) workplace (a .NET shop) suffers from an over-abundance of anemic domain models, to the extent that I don’t really know how validation and data persistence should be handled in a proper domain model.
Validation and data persistence in a domain model
My (first and current) workplace (a .NET shop) suffers from an over-abundance of anemic domain models, to the extent that I don’t really know how validation and data persistence should be handled in a proper domain model.
How to deal with data on the model specific to the technology being used?
There are some cases where some of the data on a class of the domain model of an application seems to be dependent on the technology being used. One example of this is the following: suppose we are building one application in .NET such that there’s the need of an Employee class. Suppose further that we are going to implement relational database, then the Employee has a primary key right? So that the classe would be something like
How to deal with data on the model specific to the technology being used?
There are some cases where some of the data on a class of the domain model of an application seems to be dependent on the technology being used. One example of this is the following: suppose we are building one application in .NET such that there’s the need of an Employee class. Suppose further that we are going to implement relational database, then the Employee has a primary key right? So that the classe would be something like