Tag: model

I have a doubt about the repository model and the service layer.

For See the layer I have a controller that creates an interface from ViewModels DTO (View) and my EntityModels (DataLayer). It is properly separated and the controller / service works with models that correctly use mappers.

Example:

//Model DTO
class LoginRequestDTO {
   public Username { get; set; }
   public Password { get; set; }
}

//Entity Model
class LoggedUserEntity {
   public ID { get; set; }
   public Username { get; set; }
}

For service / repository I wonder if the service method should take an entity model (data layer) as an argument or another model (from my business layer), and then map BusinessModel to EntityModel.

Example:

//Model DTO (came from another lib)
class User {
   public Name { get; set; }
   public OptionalValue { get; set; }
}

//Entity Model
class UserEntity {
   public ID { get; set; }
   public Username { get; set; }
   public GenericParameter { get; set; }
}

What should I do correctly?

Solution 1

Utility.cs
void execRoutine() {
    User user = someRoutineInAnotherLibs.getUser();
    var mappedUserEntity = Mapper.convertUserToUserEntity(user);
    serviceUser.saveUser(mappedUserEntity);
}


ServiceUser.cs
void saveUser(UserEntity u) {
    repo.insert(u);
}

Solution 2

Utility.cs
void execRoutine() {
    User user = someRoutineInAnotherLibs.getUser();
    serviceUser.saveUser(user);
}


ServiceUser.cs
void saveUser(User u) {
    var mappedUserEntity = Mapper.convertUserToUserEntity(user);
    repo.insert(u);
}

In Solution 1, I should provide UserEntity to Service and insert a service insert directly into the database.

In Solution 2, I should provide a user to the service, which converts a template to another template, and then inserts it into the database.

In each case, I do not need to know the implementation of User or UserEntity, because I have a mapper who knows how to map one model to another, so I think I do not violate the SRP.